Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2019-19333

Stack-based Buffer Overflow

Published: Dec 06, 2019 | Modified: Nov 21, 2024
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
8.1 IMPORTANT
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2019-19333
CWEhttps://cwe.mitre.org/data/definitions/121.html

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.

Weakness

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Affected Software

Name Vendor Start Version End Version
Libyang Cesnet 0.11-r1 (including) 0.11-r1 (including)
Libyang Cesnet 0.11-r2 (including) 0.11-r2 (including)
Libyang Cesnet 0.12-r1 (including) 0.12-r1 (including)
Libyang Cesnet 0.12-r2 (including) 0.12-r2 (including)
Libyang Cesnet 0.13-r1 (including) 0.13-r1 (including)
Libyang Cesnet 0.13-r2 (including) 0.13-r2 (including)
Libyang Cesnet 0.14-r1 (including) 0.14-r1 (including)
Libyang Cesnet 0.15-r1 (including) 0.15-r1 (including)
Libyang Cesnet 0.16-r1 (including) 0.16-r1 (including)
Libyang Cesnet 0.16-r2 (including) 0.16-r2 (including)
Libyang Cesnet 0.16-r3 (including) 0.16-r3 (including)
Libyang Cesnet 1.0-r1 (including) 1.0-r1 (including)
Libyang Cesnet 1.0-r2 (including) 1.0-r2 (including)
Libyang Cesnet 1.0-r3 (including) 1.0-r3 (including)
Libyang Cesnet 1.0-r4 (including) 1.0-r4 (including)
Libyang Ubuntu disco *
Libyang Ubuntu eoan *
Libyang Ubuntu trusty *
Libyang Ubuntu upstream *
Red Hat Enterprise Linux 8 RedHat libyang-0:0.16.105-3.el8_1.2 *

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use