Safety CI > ainich/politraf

pyup-update-psutil-5.4.6-to-5.9.0

3 years, 10 months ago

5d85b8ce

Update psutil from 5.4.6 to 5.9.0

pyyaml 3.13 has known security vulnerabilities.

Package

Installed

Affected

Info

pyyaml

3.13

<4

show

Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.

pyyaml

3.13

<5.3.1

show

Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.

pyyaml

3.13

<5.4

show

Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
https://bugzilla.redhat.com/show_bug.cgi?id=1860466

pyup-pin-infi.clickhouse_orm-2.1.1

3 years, 10 months ago

acd3bccd

Pin infi.clickhouse_orm to latest version 2.1.1

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-vulners-1.1.1-to-2.0.0

3 years, 10 months ago

c61e1ed9

Update vulners from 1.1.1 to 2.0.0

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-pyyaml-3.13-to-6.0

3 years, 10 months ago

33295850

Update pyyaml from 3.13 to 6.0

psutil 5.4.6 has known security vulnerabilities.

Package	Installed	Affected	Info
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

Package

Installed

Affected

Info

psutil

5.4.6

<=5.6.5

show

psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-vulners-1.1.1-to-1.5.13

4 years, 2 months ago

6ff88b43

Update vulners from 1.1.1 to 1.5.13

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-vulners-1.1.1-to-1.5.12

4 years, 2 months ago

17d4a682

Update vulners from 1.1.1 to 1.5.12

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-otxv2-1.2-to-1.5.12

4 years, 7 months ago

731a90bf

Update otxv2 from 1.2 to 1.5.12

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-vulners-1.1.1-to-1.5.11

4 years, 7 months ago

f4bad6a2

Update vulners from 1.1.1 to 1.5.11

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-pyshark-0.4.1-to-0.4.3

4 years, 7 months ago

d8a25c61

Update pyshark from 0.4.1 to 0.4.3

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

dependabot/pip/pyyaml-5.4

4 years, 7 months ago

191bfa03

build(deps): bump pyyaml from 3.13 to 5.4 Bumps [pyyaml](https://github.com/yaml/pyyaml) from 3.13

psutil 5.4.6 has known security vulnerabilities.

Package	Installed	Affected	Info
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

Package

Installed

Affected

Info

psutil

5.4.6

<=5.6.5

show

psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-pyyaml-3.13-to-5.4.1

4 years, 9 months ago

afbd6ce4

Update pyyaml from 3.13 to 5.4.1

psutil 5.4.6 has known security vulnerabilities.

Package	Installed	Affected	Info
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

Package

Installed

Affected

Info

psutil

5.4.6

<=5.6.5

show

psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-pyyaml-3.13-to-5.4

4 years, 9 months ago

1c107e28

Update pyyaml from 3.13 to 5.4

psutil 5.4.6 has known security vulnerabilities.

Package	Installed	Affected	Info
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

Package

Installed

Affected

Info

psutil

5.4.6

<=5.6.5

show

psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.

pyup-update-psutil-5.4.6-to-5.8.0

4 years, 10 months ago

ab54358d

Update psutil from 5.4.6 to 5.8.0

pyyaml 3.13 has known security vulnerabilities.

Package

Installed

Affected

Info

pyyaml

3.13

<4

show

Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.

pyyaml

3.13

<5.3.1

show

Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.

pyyaml

3.13

<5.4

show

Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
https://bugzilla.redhat.com/show_bug.cgi?id=1860466

pyup-update-psutil-5.4.6-to-5.7.3

5 years ago

85012fbc

Update psutil from 5.4.6 to 5.7.3

pyyaml 3.13 has known security vulnerabilities.

Package

Installed

Affected

Info

pyyaml

3.13

<4

show

Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.

pyyaml

3.13

<5.3.1

show

Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.

pyyaml

3.13

<5.4

show

Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
https://bugzilla.redhat.com/show_bug.cgi?id=1860466

pyup-update-vulners-1.1.1-to-1.5.9

5 years ago

3e3cd434

Update vulners from 1.1.1 to 1.5.9

pyyaml 3.13 and psutil 5.4.6 have known security vulnerabilities.

Package	Installed	Affected	Info
pyyaml	3.13	<4	show Pyyaml before 4 uses ``yaml.load`` which has been assigned CVE-2017-18342.
pyyaml	3.13	<5.3.1	show Pyyaml 5.3.1 includes a fix for CVE-2020-1747: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
pyyaml	3.13	<5.4	show Pyyaml version 5.4 includes a fix for CVE-2020-14343: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. https://bugzilla.redhat.com/show_bug.cgi?id=1860466
psutil	5.4.6	<=5.6.5	show psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. See CVE-2019-18874.