Skip to content
Fencer Vulns
high 8.1

CVE-2019-19333 json

In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of…

published 2019-12-06 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-8954

cvss
8.1
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.6%
EPSS 3.6% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of type "bits". An application that uses libyang to parse untrusted YANG files may be vulnerable to this flaw, which would allow an attacker to cause a denial of service or possibly gain code execution.

Patch / fix

  • libyang Debian 14, Debian 13 0.16.105-2

debian advisories DEBIAN-CVE-2019-19333

  • libyang RHEL 8 0.16.105-3.el8_1.2

red hat advisories RHSA-2019:4360

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-2019-19333 updated cvss 8.1

libyang: stack-based buffer overflow in make_canonical when bits leaf type is used

  • Red Hat Enterprise Linux AppStream (v. 8) libyang 0.16.105-3.el8_1.2
    fixed: vendor fix RHSA-2019:4360

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

3.64% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Red Hat libyang

Classification

Weakness

References

Sources

Fencer Vulns 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.