Skip to content
Fencer Intel
medium 6.8

CVE-2013-6393 json

Heap Based Buffer Overflow in libyaml

published 12y ago modified 4mo ago also GHSA-m75h-cghq-c8h5 , EUVD-2020-0633

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.4%
EPSS 7.4% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

The yaml_parser_scan_tag_uri function in scanner.c in LibYAML before 0.1.5 performs an incorrect cast, which allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via crafted tags in a YAML document, which triggers a heap-based buffer overflow.

Patch / fix

  • npm libyaml 0.2.3
  • libyaml Debian 14, Debian 13, Debian 12 0.1.4-3
  • libyaml-libyaml-perl Debian 14, Debian 13, Debian 12 0.41-4

debian advisories DEBIAN-CVE-2013-6393

  • ruby193-libyaml RHEL 1 SOFTWARE_COLLECTIONS, openstack 3 0.1.4-5.1.el6
  • libyaml RHEL 6 COMMON, openstack 4, openstack 3 0.1.3-1.4.el6

red hat advisories RHSA-2014:0364RHSA-2014:0353RHSA-2014:0354RHSA-2014:0355RHSA-2014:0415

  • perl-YAML-LibYAML SLES 12, SLED 12, SLES for SAP 12 0.38-10.1

suse advisories SUSE-SU-2015:0953-1SUSE-SU-2015:0953-2

  • libyaml openSUSE Tumbleweed 0.1.6-4.8
  • perl-YAML-LibYAML openSUSE Tumbleweed 0.59-2.11

opensuse advisories openSUSE-SU-2024:10029-1openSUSE-SU-2024:10520-1

Is CVE-2013-6393 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-6393 updated cvss 4.3

libyaml: heap-based buffer overflow when parsing YAML tags

  • Red Hat OpenShift Enterprise 1 ruby193-libyaml
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 libyaml
    affected: workaround, no fix available
  • Red Hat Enterprise MRG 1 libyaml Red Hat Enterprise MRG 2 libyaml Red Hat Satellite 5 libyaml
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Software Collections libyaml
    affected: workaround, no fix available
  • Red Hat Subscription Asset Manager libyaml
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Common for RHEL Server (v. 6) libyaml 0.1.3-1.4.el6
    fixed: vendor fix RHSA-2014:0415
  • Red Hat Enterprise Linux OpenStack Platform 3.0 libyaml 0.1.3-1.4.el6, ruby193-libyaml 0.1.4-5.1.el6
    fixed: vendor fix RHSA-2014:0353
  • Red Hat Enterprise Linux OpenStack Platform 4.0 libyaml 0.1.3-1.4.el6
    fixed: vendor fix RHSA-2014:0354
show 2 more
  • Red Hat Software Collections 1 for Red Hat Enterprise Linux Server (v. 6) ruby193-libyaml 0.1.4-5.1.el6 Red Hat Software Collections 1 for Red Hat Enterprise Linux Workstation (v. 6) ruby193-libyaml 0.1.4-5.1.el6
    fixed: vendor fix RHSA-2014:0355
  • Red Hat CloudForms Management Engine 5 ruby193-libyaml Red Hat Enterprise Linux 7 libyaml Red Hat Satellite 6 libyaml, ruby193-libyaml
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.39% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
npm libyaml
<0.2.3
0.2.3

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.