| 1 |
pinkbyte 14/05/23 08:42:42 |
| 2 |
|
| 3 |
Added: glsa-201405-27.xml |
| 4 |
Log: |
| 5 |
GLSA 201405-27 |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.1 xml/htdocs/security/en/glsa/glsa-201405-27.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201405-27.xml?rev=1.1&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201405-27.xml?rev=1.1&content-type=text/plain |
| 12 |
|
| 13 |
Index: glsa-201405-27.xml |
| 14 |
=================================================================== |
| 15 |
<?xml version="1.0" encoding="UTF-8"?> |
| 16 |
<?xml-stylesheet href="/xsl/glsa.xsl" type="text/xsl"?> |
| 17 |
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> |
| 18 |
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd"> |
| 19 |
<glsa id="201405-27"> |
| 20 |
<title>LibYAML: Arbitrary code execution</title> |
| 21 |
<synopsis>A vulnerability in LibYAML could allow an attacker to execute |
| 22 |
arbitrary code or cause a Denial of Service condition. |
| 23 |
</synopsis> |
| 24 |
<product type="ebuild">libyaml</product> |
| 25 |
<announced>May 23, 2014</announced> |
| 26 |
<revised>May 23, 2014: 1</revised> |
| 27 |
<bug>505948</bug> |
| 28 |
<access>local, remote</access> |
| 29 |
<affected> |
| 30 |
<package name="dev-libs/libyaml" auto="yes" arch="*"> |
| 31 |
<unaffected range="ge">0.1.6</unaffected> |
| 32 |
<vulnerable range="lt">0.1.6</vulnerable> |
| 33 |
</package> |
| 34 |
</affected> |
| 35 |
<background> |
| 36 |
<p>LibYAML is a YAML 1.1 parser and emitter written in C.</p> |
| 37 |
</background> |
| 38 |
<description> |
| 39 |
<p>The yaml_parser_scan_uri_escapes() function does not properly expand |
| 40 |
strings passed as input, which can result in a heap-based buffer |
| 41 |
overflow. |
| 42 |
</p> |
| 43 |
</description> |
| 44 |
<impact type="normal"> |
| 45 |
<p>An attacker could provide a specially-crafted YAML document, which, when |
| 46 |
parsed by LibYAML, could result in arbitrary code execution or cause the |
| 47 |
application to crash. |
| 48 |
</p> |
| 49 |
</impact> |
| 50 |
<workaround> |
| 51 |
<p>There is no known workaround at this time.</p> |
| 52 |
</workaround> |
| 53 |
<resolution> |
| 54 |
<p>All LibYAML users should upgrade to the latest version:</p> |
| 55 |
|
| 56 |
<code> |
| 57 |
# emerge --sync |
| 58 |
# emerge --ask --oneshot --verbose ">=dev-libs/libyaml-0.1.6" |
| 59 |
</code> |
| 60 |
|
| 61 |
<p>Packages which depend on this library may need to be recompiled. Tools |
| 62 |
such as revdep-rebuild may assist in identifying these packages. |
| 63 |
</p> |
| 64 |
</resolution> |
| 65 |
<references> |
| 66 |
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-2525">CVE-2014-2525</uri> |
| 67 |
</references> |
| 68 |
<metadata tag="requester" timestamp="Thu, 15 May 2014 03:39:38 +0000"> |
| 69 |
BlueKnight |
| 70 |
</metadata> |
| 71 |
<metadata tag="submitter" timestamp="Fri, 23 May 2014 08:42:20 +0000"> |
| 72 |
creffett |
| 73 |
</metadata> |
| 74 |
</glsa> |
Archives