CWE
119
Advisory Published
Updated

CVE-2014-2525: Buffer Overflow

First published: Fri Mar 28 2014(Updated: )

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.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
libyaml<=0.1.5
libyaml=0.0.1
libyaml=0.1.1
libyaml=0.1.2
libyaml=0.1.3
libyaml=0.1.4
SUSE Linux=42.1
openSUSE=13.1
openSUSE=13.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2014-2525?

    CVE-2014-2525 has a high severity rating due to its potential to allow arbitrary code execution via a vulnerability in the parsing of URIs.

  • How do I fix CVE-2014-2525?

    To fix CVE-2014-2525, update LibYAML to version 0.1.6 or later, which contains the necessary security patches.

  • What versions of LibYAML are affected by CVE-2014-2525?

    CVE-2014-2525 affects LibYAML versions prior to 0.1.6, including all versions between 0.0.1 and 0.1.5.

  • Can CVE-2014-2525 be exploited remotely?

    Yes, CVE-2014-2525 can be exploited by attackers via crafted YAML files containing specially encoded URIs.

  • What is the impact of CVE-2014-2525 on applications using LibYAML?

    Applications using affected versions of LibYAML are vulnerable to remote code execution, posing a significant security risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203