From 4f2d7949f03e1c198bc888f2d05f421d35c57e21 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Mon, 9 Oct 2017 18:53:29 +0100 Subject: reinit the tree, so we can have metadata --- metadata/glsa/glsa-201403-02.xml | 53 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 metadata/glsa/glsa-201403-02.xml (limited to 'metadata/glsa/glsa-201403-02.xml') diff --git a/metadata/glsa/glsa-201403-02.xml b/metadata/glsa/glsa-201403-02.xml new file mode 100644 index 000000000000..12f189d13e51 --- /dev/null +++ b/metadata/glsa/glsa-201403-02.xml @@ -0,0 +1,53 @@ + + + + LibYAML: Arbitrary code execution + A Vulnerability in LibYAML could result in execution of arbitrary + code. + + libyaml + 2014-03-08 + 2014-03-08: 1 + 499920 + remote + + + 0.1.5 + 0.1.5 + + + +

LibYAML is a YAML 1.1 parser and emitter written in C.

+
+ +

A heap-based buffer overflow flaw was found in the way libyaml parsed + YAML tags. +

+
+ +

A remote attacker could provide a specially-crafted YAML document which + when parsed by LibYAML, would cause the application to crash or, + potentially, execute arbitrary code with the privileges the user who is + running the application. +

+
+ +

There is no known workaround at this time.

+
+ +

All LibYAML users should upgrade to the latest version:

+ + + # emerge --sync + # emerge --ask --oneshot --verbose ">=dev-libs/libyaml-0.1.5" + + +
+ + CVE-2013-6393 + + Zlogene + + BlueKnight + +
-- cgit v1.2.3