aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJosh Paetzel <jpaetzel@FreeBSD.org>2019-04-24 15:30:40 +0000
committerJosh Paetzel <jpaetzel@FreeBSD.org>2019-04-24 15:30:40 +0000
commit6765ea38d986fb07ebad258860928361c30e47e1 (patch)
tree5cee06fe30c7d3345d570161f7f9941558576cc6
parentf8b4e20618eaf3b299ac7233c715dbc05d751cdf (diff)
downloadports-6765ea38d986fb07ebad258860928361c30e47e1.tar.gz
ports-6765ea38d986fb07ebad258860928361c30e47e1.zip
Document py-yaml vulnerability
PR: 237501 Submitted by: sergey@akhmatov.ru Security: CVE-2017-18342
Notes
Notes: svn path=/head/; revision=499855
-rw-r--r--security/vuxml/vuln.xml31
1 files changed, 31 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml
index 94864f448ada..101ccd9a1b06 100644
--- a/security/vuxml/vuln.xml
+++ b/security/vuxml/vuln.xml
@@ -58,6 +58,37 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+ <vuln vid="f6ea18bb-65b9-11e9-8b31-002590045d9c">
+ <topic>py-yaml -- arbitrary code execution</topic>
+ <affects>
+ <package>
+ <name>py27-yaml</name>
+ <name>py35-yaml</name>
+ <name>py36-yaml</name>
+ <name>py37-yaml</name>
+ <range><lt>4.1</lt></range>
+ </package>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p>pyyaml reports:</p>
+ <blockquote cite="https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation">
+ <p>the PyYAML.load function could be easily exploited to call any Python
+ function. That means it could call any system command using os.system()</p>
+ </blockquote>
+ </body>
+ </description>
+ <references>
+ <cvename>CVE-2017-18342</cvename>
+ <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18342</url>
+ <url>https://github.com/yaml/pyyaml/pull/74</url>
+ </references>
+ <dates>
+ <discovery>2018-06-27</discovery>
+ <entry>2019-04-23</entry>
+ </dates>
+ </vuln>
+
<vuln vid="a207bbd8-6572-11e9-8e67-206a8a720317">
<topic>FreeBSD -- EAP-pwd message reassembly issue with unexpected fragment</topic>
<affects>