Safety CI > ainich/politraf

pyup-update-psutil-5.4.6-to-7.1.2

5 days, 2 hours ago

0ad938ba

Update psutil from 5.4.6 to 7.1.2

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-7.1.1

1 week, 3 days ago

adb782a4

Update psutil from 5.4.6 to 7.1.1

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-pyyaml-3.13-to-6.0.3

1 month ago

23d42eff

Update pyyaml from 3.13 to 6.0.3

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-3.1.1

1 month, 1 week ago

057e7a03

Update vulners from 1.1.1 to 3.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-psutil-5.4.6-to-7.1.0

1 month, 1 week ago

1ecc1bbb

Update psutil from 5.4.6 to 7.1.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-vulners-1.1.1-to-2.3.6

8 months, 1 week ago

5d373411

Update vulners from 1.1.1 to 2.3.6

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.3.4

8 months, 2 weeks ago

415afa98

Update vulners from 1.1.1 to 2.3.4

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-psutil-5.4.6-to-7.0.0

8 months, 2 weeks ago

99b42955

Update psutil from 5.4.6 to 7.0.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-vulners-1.1.1-to-2.3.3

8 months, 3 weeks ago

4165f522

Update vulners from 1.1.1 to 2.3.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.

pyup-update-vulners-1.1.1-to-2.3.2

8 months, 4 weeks ago

15d27a64

Update vulners from 1.1.1 to 2.3.2

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.3.1

8 months, 4 weeks ago

a7979acf

Update vulners from 1.1.1 to 2.3.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.3.0

9 months ago

9096347c

Update vulners from 1.1.1 to 2.3.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-psutil-5.4.6-to-6.1.1

10 months, 2 weeks ago

5d85101f

Update psutil from 5.4.6 to 6.1.1

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-2.2.3

1 year ago

41939509

Update vulners from 1.1.1 to 2.2.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.

pyup-update-psutil-5.4.6-to-6.1.0

1 year ago

b9a22433

Update psutil from 5.4.6 to 6.1.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