Skip to content
Noroxi
CVE-2014-9130· NVD / CVE Program· CNA mitre

scanner.c in LibYAML 0.1.5 and 0.1.6, as used in the YAML-LibYAML (aka YAML-XS) module for Perl, allows context-dependent attackers to cause

scanner.c in LibYAML 0.1.5 and 0.1.6, as used in the YAML-LibYAML (aka YAML-XS) module for Perl, allows context-dependent attackers to cause a denial of service (assertion failure and crash) via vectors involving line-wrapping.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Dec 8, 2014
Updated
Jun 16, 2026
EPSS
13.2% · 96th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
4 / 30 · 13.2%

Affected systems

VendorProduct
pyyamllibyaml

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • pyyaml libyaml0.1.5
  • pyyaml libyaml0.1.6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.4yamlbefore 0.1.6-r10.1.6-r1
Debian:12libyamlbefore 0.1.6-30.1.6-3
Debian:12libyaml-libyaml-perlbefore 0.41-60.41-6
Debian:12pyyamlbefore 3.11-23.11-2
Debian:6.0libyamlbefore 0.1.3-1+deb6u50.1.3-1+deb6u5
Debian:6.0libyaml-libyaml-perlbefore 0.33-1+squeeze40.33-1+squeeze4
Debian:6.0pyyamlbefore 3.09-5+deb6u13.09-5+deb6u1
Debian:7libyamlbefore 0.1.4-2+deb7u50.1.4-2+deb7u5
Debian:7libyaml-libyaml-perlbefore 0.38-3+deb7u30.38-3+deb7u3
Debian:7pyyamlbefore 3.10-4+deb7u13.10-4+deb7u1
openSUSE:Tumbleweedlibyamlbefore 0.1.6-4.80.1.6-4.8
openSUSE:Tumbleweedperl-YAML-LibYAMLbefore 0.59-2.110.59-2.11
Red Hat:enterprise_linux:6::clientlibyamlbefore 0:0.1.3-4.el6_60:0.1.3-4.el6_6
Red Hat:enterprise_linux:6::clientlibyaml-debuginfobefore 0:0.1.3-4.el6_60:0.1.3-4.el6_6
Red Hat:enterprise_linux:6::clientlibyaml-develbefore 0:0.1.3-4.el6_60:0.1.3-4.el6_6
Red Hat:enterprise_linux:7::clientlibyamlbefore 0:0.1.4-11.el7_00:0.1.4-11.el7_0
Red Hat:enterprise_linux:7::clientlibyaml-debuginfobefore 0:0.1.4-11.el7_00:0.1.4-11.el7_0
Red Hat:enterprise_linux:7::clientlibyaml-develbefore 0:0.1.4-11.el7_00:0.1.4-11.el7_0
SUSE:Linux Enterprise High Availability Extension 12python-PyYAMLbefore 3.10-15.13.10-15.1
SUSE:Linux Enterprise Server 12perl-YAML-LibYAMLbefore 0.38-10.10.38-10.1

Other highest-scoring records for the same primary product.

  • CVE-2014-2525Heap-based buffer overflow in the yaml_parser_scan_uri_escapes function in LibYAML before 0.1.6 allows context-dependent attackers to execut
    30Monitor
  • CVE-2013-6393The yaml_parser_scan_tag_uri function in scanner.c in LibYAML before 0.1.5 performs an incorrect cast, which allows remote attackers to caus
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:yaml0.1.6-r1 · Alpine:v3.4Package registry (OSV)
debian:libyaml0.1.6-3 · Debian:12Package registry (OSV)
debian:libyaml-libyaml-perl0.41-6 · Debian:12Package registry (OSV)
debian:pyyaml3.11-2 · Debian:12Package registry (OSV)
opensuse:libyaml0.1.6-4.8 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:perl-YAML-LibYAML0.59-2.11 · openSUSE:TumbleweedPackage registry (OSV)
red hat:libyaml0:0.1.3-4.el6_6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:libyaml-debuginfo0:0.1.3-4.el6_6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:libyaml-devel0:0.1.3-4.el6_6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
suse:perl-YAML-LibYAML0.38-10.1 · SUSE:Linux Enterprise Server 12Package registry (OSV)
suse:python-PyYAML3.10-15.1 · SUSE:Linux Enterprise High Availability Extension 12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records