Lines 58-63
Link Here
|
58 |
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.) |
58 |
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.) |
59 |
--> |
59 |
--> |
60 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
60 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
|
|
61 |
<vuln vid="f6ea18bb-65b9-11e9-8b31-002590045d9c"> |
62 |
<topic>py-yaml -- arbitrary code execution</topic> |
63 |
<affects> |
64 |
<package> |
65 |
<name>py27-yaml</name> |
66 |
<name>py35-yaml</name> |
67 |
<name>py36-yaml</name> |
68 |
<name>py37-yaml</name> |
69 |
<range><lt>4.1</lt></range> |
70 |
</package> |
71 |
</affects> |
72 |
<description> |
73 |
<body xmlns="http://www.w3.org/1999/xhtml"> |
74 |
<p>pyyaml reports:</p> |
75 |
<blockquote cite="https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation"> |
76 |
<p>the PyYAML.load function could be easily exploited to call any Python |
77 |
function. That means it could call any system command using os.system()</p> |
78 |
</blockquote> |
79 |
</body> |
80 |
</description> |
81 |
<references> |
82 |
<cvename>CVE-2017-18342</cvename> |
83 |
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18342</url> |
84 |
<url>https://github.com/yaml/pyyaml/pull/74</url> |
85 |
</references> |
86 |
<dates> |
87 |
<discovery>2018-06-27</discovery> |
88 |
<entry>2019-04-23</entry> |
89 |
</dates> |
90 |
</vuln> |
91 |
|
61 |
<vuln vid="a207bbd8-6572-11e9-8e67-206a8a720317"> |
92 |
<vuln vid="a207bbd8-6572-11e9-8e67-206a8a720317"> |
62 |
<topic>FreeBSD -- EAP-pwd message reassembly issue with unexpected fragment</topic> |
93 |
<topic>FreeBSD -- EAP-pwd message reassembly issue with unexpected fragment</topic> |
63 |
<affects> |
94 |
<affects> |