Document vulnerabilities in GNU cpio < 2.13.

This commit is contained in:
Christian Weisgerber 2019-11-15 22:46:16 +00:00
parent 278e78cfc4
commit e7ea6c1e1b
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=517704

View File

@ -58,6 +58,42 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
<vuln vid="f59af308-07f3-11ea-8c56-f8b156b6dcc8">
<topic>GNU cpio -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gcpio</name>
<range><lt>2.13</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Sergey Poznyakoff reports:</p>
<blockquote cite="https://lists.gnu.org/archive/html/bug-cpio/2019-11/msg00000.html">
<p>This stable release fixes several potential vulnerabilities</p>
<p>CVE-2015-1197: cpio, when using the --no-absolute-filenames
option, allows local users to write to arbitrary files
via a symlink attack on a file in an archive.</p>
<p>CVE-2016-2037: The cpio_safer_name_suffix function in
util.c allows remote attackers to cause a denial of service
(out-of-bounds write) via a crafted cpio file.</p>
<p>CVE-2019-14866: Improper input validation when writing
tar header fields leads to unexpected tar generation.</p>
</blockquote>
</body>
</description>
<references>
<url>https://lists.gnu.org/archive/html/bug-cpio/2019-11/msg00000.html</url>
<cvename>CVE-2015-1197</cvename>
<cvename>CVE-2016-2037</cvename>
<cvename>CVE-2019-14866</cvename>
</references>
<dates>
<discovery>2019-11-06</discovery>
<entry>2019-11-15</entry>
</dates>
</vuln>
<vuln vid="b48e7b14-052a-11ea-a1de-53b029d2b061">
<topic>libmad -- multiple vulnerabilities</topic>
<affects>