Upstream has issued an advisory on March 26: http://openwall.com/lists/oss-security/2014/03/26/12 The issue is fixed upstream in 0.1.6 and the commit is also linked there. Reproducible: Steps to Reproduce:
Whiteboard: (none) => MGA4TOO, MGA3TOO
Debian has issued an advisory for this on March 26: http://www.debian.org/security/2014/dsa-2884
URL: (none) => http://www.debian.org/security/2014/dsa-2884
URL: http://www.debian.org/security/2014/dsa-2884 => http://lwn.net/Vulnerabilities/592273/
Status: NEW => ASSIGNED
fixed in cauldron, mga3 and mga4 uploaded into upgrades_testing, both mga3 and mga4, 32 and 64bit: yaml-0.1.6-1.mga5.src.rpm lib64yaml0_2-0.1.6-1.mgax.x86_64.rpm lib64yaml-devel-0.1.6-1.mgax.x86_64.rpm yaml-debuginfo-0.1.6-1.mgax.x86_64.rpm
CC: (none) => thomasAssignee: thomas => qa-bugs
Thanks Thomas! Advisory: ======================== Updated libyaml packages fix security vulnerabilities: Ivan Fratric of the Google Security Team discovered a heap-based buffer overflow vulnerability in LibYAML, a fast YAML 1.1 parser and emitter library. A remote attacker could provide a specially-crafted YAML document that, when parsed by an application using libyaml, would cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application (CVE-2014-2525). References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-2525 http://www.debian.org/security/2014/dsa-2884 ======================== Updated packages in core/updates_testing: ======================== libyaml0_2-0.1.6-1.mga3 libyaml-devel-0.1.6-1.mga3 yaml-debuginfo-0.1.6-1.mga3 libyaml0_2-0.1.6-1.mga4 libyaml-devel-0.1.6-1.mga4 yaml-debuginfo-0.1.6-1.mga4 from SRPMS: yaml-0.1.6-1.mga3.src.rpm yaml-0.1.6-1.mga4.src.rpm
Version: Cauldron => 4Whiteboard: MGA4TOO, MGA3TOO => MGA3TOO
You can find information on how to test this in Bug 12583.
Severity: normal => critical
Advisory 13101.adv committed to svn.
CC: (none) => davidwhodginsWhiteboard: MGA3TOO => MGA3TOO advisory
Procedure at the end of comment 3 here https://bugs.mageia.org/show_bug.cgi?id=12583#c3
Whiteboard: MGA3TOO advisory => MGA3TOO advisory has_procedure
Testing complete on Mageia 3 i586 and Mageia 4 i586 using Comment 6.
Whiteboard: MGA3TOO advisory has_procedure => MGA3TOO advisory has_procedure MGA3-32-OK MGA4-32-OK
Testing complete mga3 64 and mga4 64 Output from the example is different in mga3 than it is mga4. In mga3 it is all on one line showing '\n' instead of creating newlines. There are spaces after the \n's which would create correct indentation if they were on new lines though. It is the same before and after the update so validating. Advisory previously uploaded. Could sysadmin please push to 3 & 4 updates Thanks
Keywords: (none) => validated_updateWhiteboard: MGA3TOO advisory has_procedure MGA3-32-OK MGA4-32-OK => MGA3TOO advisory has_procedure MGA3-32-OK mga3-64-ok MGA4-32-OK mga4-64-okCC: (none) => sysadmin-bugs
http://advisories.mageia.org/MGASA-2014-0150.html
Status: ASSIGNED => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED