Pyyaml LibYAML up to 0.1.5 Parser yaml_parser_scan_uri_escapes memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Pyyaml LibYAML up to 0.1.5. It has been classified as critical. Affected is the function yaml_parser_scan_uri_escapes of the component Parser. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2014-2525. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Pyyaml LibYAML up to 0.1.5. It has been classified as critical. This affects the function yaml_parser_scan_uri_escapes of the component Parser. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Heap-based buffer overflow in the yaml_parser_scan_uri_escapes function in LibYAML before 0.1.6 allows context-dependent attackers to execute arbitrary code via a long sequence of percent-encoded characters in a URI in a YAML file.

The weakness was presented 03/28/2014 by Security Team with Google Security Team as confirmed advisory (CERT.org). The advisory is shared at ocert.org. This vulnerability is uniquely identified as CVE-2014-2525 since 03/17/2014. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 74171 (GLSA-201405-27 : LibYAML: Arbitrary code execution), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 350407 (Amazon Linux Security Advisory for perl-YAML-LibYAML: ALAS-2014-324).

Upgrading to version 0.1.2 eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (74171), SecurityFocus (BID 66478†) and Secunia (SA57836†). See VDB-12693, VDB-67663 and VDB-65652 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 74171
Nessus Name: GLSA-201405-27 : LibYAML: Arbitrary code execution
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 10994
OpenVAS Name: Gentoo Linux Local Check: https://security.gentoo.org/glsa/201405-27
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: LibYAML 0.1.2

Timelineinfo

03/17/2014 🔍
03/26/2014 +9 days 🔍
03/28/2014 +2 days 🔍
03/28/2014 +0 days 🔍
04/15/2014 +18 days 🔍
05/23/2014 +38 days 🔍
05/25/2014 +2 days 🔍
03/24/2015 +303 days 🔍
05/09/2026 +4064 days 🔍

Sourcesinfo

Advisory: USN-2160-1
Researcher: Security Team
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2014-2525 (🔍)
GCVE (CVE): GCVE-0-2014-2525
GCVE (VulDB): GCVE-100-66813

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 66478 - LibYAML 'yaml_parser_scan_uri_escapes()' Function Remote Heap Based Buffer Overflow Vulnerability
Secunia: 57836 - Chef Multiple Vulnerabilities, Moderately Critical

See also: 🔍

Entryinfo

Created: 03/24/2015 15:54
Updated: 05/09/2026 05:40
Changes: 03/24/2015 15:54 (77), 05/02/2019 18:53 (6), 02/06/2022 12:23 (3), 02/06/2022 12:31 (1), 05/09/2026 05:40 (15)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!