Safety CI > ainich/politraf

pyup-pin-infi.clickhouse_orm-2.1.2

3 years, 8 months ago

d442d06b

Pin infi.clickhouse_orm to latest version 2.1.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.
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

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.

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

3 years, 8 months ago

e84004ca

Update pyshark from 0.4.1 to 0.5.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.
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

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.

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

3 years, 9 months ago

edad5780

Update pyshark from 0.4.1 to 0.5.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.
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

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.

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

3 years, 9 months ago

f59ad036

Update pyshark from 0.4.1 to 0.5.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.
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

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.

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

3 years, 9 months ago

969f5997

Update pyshark from 0.4.1 to 0.5

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

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.

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

3 years, 10 months ago

ddc02fbe

Update pyshark from 0.4.1 to 0.4.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.
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

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.

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

3 years, 10 months ago

ae1a98fb

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

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.

pyup-update-vulners-1.1.1-to-2.0.2

4 years, 1 month ago

74204fd1

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

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.

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

4 years, 2 months ago

d8289d3d

Update pyshark from 0.4.1 to 0.4.5

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

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.

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

4 years, 2 months ago

4e0c29ff

Update pyshark from 0.4.1 to 0.4.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.
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

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.

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

4 years, 3 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.

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.

pyup-pin-infi.clickhouse_orm-2.1.1

4 years, 3 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.
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

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.

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

4 years, 3 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.
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

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.

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

4 years, 3 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, 7 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.
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

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.

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.