- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201403-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: LibYAML: Arbitrary code execution
     Date: March 08, 2014
     Bugs: #499920
       ID: 201403-02

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
A Vulnerability in LibYAML could result in execution of arbitrary code.

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

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-libs/libyaml             < 0.1.5                    >= 0.1.5 

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

Impact
=====
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.

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All LibYAML users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-libs/libyaml-0.1.5"

References
=========
[ 1 ] CVE-2013-6393
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-6393

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/201403-02

Concerns?
========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
======
Copyright 2014 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/


Gentoo: GLSA-201403-02: LibYAML: Arbitrary code execution

A Vulnerability in LibYAML could result in execution of arbitrary code.

Summary

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

Resolution

All LibYAML users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libyaml-0.1.5"

References

[ 1 ] CVE-2013-6393 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-6393

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201403-02

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Normal
Title: LibYAML: Arbitrary code execution
Date: March 08, 2014
Bugs: #499920
ID: 201403-02

Synopsis

A Vulnerability in LibYAML could result in execution of arbitrary code.

Background

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

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-libs/libyaml < 0.1.5 >= 0.1.5

Impact

===== 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.

Workaround

There is no known workaround at this time.

Related News