CVE-2019-20394
published 2020-01-22CVE-2019-20394: A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use…
PriorityP343high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
2.79%
84.8th percentile
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
Affected
11 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| cesnet | libyang | — | — |
| cesnet | libyang | — | — |
| cesnet | libyang | — | — |
| cesnet | libyang | — | — |
| cesnet | libyang | — | — |
| cesnet | libyang | — | — |
| cesnet | libyang | — | — |
| cesnet | libyang | >= 0 < 1.0.176-1 | 1.0.176-1 |
| cesnet | libyang | >= 0 < 1.0.176-1 | 1.0.176-1 |
| cesnet | libyang | >= 0 < 1.0.176-1 | 1.0.176-1 |
| debian | libyang | < libyang 1.0.176-1 (bullseye) | libyang 1.0.176-1 (bullseye) |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv8.8HIGH
vendor_debian8.8HIGH
vendor_redhat8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-pgmh-hmfg-8gwj: A double-free is present in libyang before v1
ghsa_unreviewed·2022-05-24
CVE-2019-20394 [MEDIUM] CWE-415 GHSA-pgmh-hmfg-8gwj: A double-free is present in libyang before v1
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
OSV
CVE-2019-20394: A double-free is present in libyang before v1
osv·2020-01-22·CVSS 8.8
CVE-2019-20394 [HIGH] CVE-2019-20394: A double-free is present in libyang before v1
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
Red Hat
libyang: double-free in yyparse() when a type statement is used in a notification statement
vendor_redhat·2019-04-26·CVSS 8.8
CVE-2019-20394 [HIGH] CWE-416 libyang: double-free in yyparse() when a type statement is used in a notification statement
libyang: double-free in yyparse() when a type statement is used in a notification statement
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
A double-free flaw occurs in libyang in function yyparse() when a type statement is used in a notification statement. Applications that use libyang to process untrusted input YANG files may be vulnerable to this flaw, possibly causing a crash or potential code execution.
Debian
CVE-2019-20394: libyang - A double-free is present in libyang before v1.0-r3 in the function yyparse() whe...
vendor_debian·2019·CVSS 8.8
CVE-2019-20394 [HIGH] CVE-2019-20394: libyang - A double-free is present in libyang before v1.0-r3 in the function yyparse() whe...
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
Scope: local
bullseye: resolved (fixed in 1.0.176-1)
forky: resolved (fixed in 1.0.176-1)
sid: resolved (fixed in 1.0.176-1)
trixie: resolved (fixed in 1.0.176-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-20394 libyang: double-free in yyparse() when a type statement is used in a notification statement [fedora-all]
bugzilla·2020-02-03·CVSS 8.8
CVE-2019-20394 [HIGH] CVE-2019-20394 libyang: double-free in yyparse() when a type statement is used in a notification statement [fedora-all]
CVE-2019-20394 libyang: double-free in yyparse() when a type statement is used in a notification statement [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this
Bugzilla
CVE-2019-20394 libyang: double-free in yyparse() when a type statement is used in a notification statement
bugzilla·2020-01-22·CVSS 8.8
CVE-2019-20394 [HIGH] CVE-2019-20394 libyang: double-free in yyparse() when a type statement is used in a notification statement
CVE-2019-20394 libyang: double-free in yyparse() when a type statement is used in a notification statement
A double-free is present in libyang up to version v1.0-r3 in function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
Upstream issue:
https://github.com/CESNET/libyang/issues/769
Upstream fix:
https://github.com/CESNET/libyang/commit/6cc51b1757dfbb7cff92de074ada65e8523289a6
Discussion:
Created libyang tracking bugs for this issue:
Affects: fedora-all [bug 1797544]
https://bugzilla.redhat.com/show_bug.cgi?id=1793932https://github.com/CESNET/libyang/commit/6cc51b1757dfbb7cff92de074ada65e8523289a6https://github.com/CESNET/libyang/compare/v1.0-r2...v1.0-r3https://github.com/CESNET/libyang/issues/769https://lists.debian.org/debian-lts-announce/2023/09/msg00019.htmlhttps://bugzilla.redhat.com/show_bug.cgi?id=1793932https://github.com/CESNET/libyang/commit/6cc51b1757dfbb7cff92de074ada65e8523289a6https://github.com/CESNET/libyang/compare/v1.0-r2...v1.0-r3https://github.com/CESNET/libyang/issues/769https://lists.debian.org/debian-lts-announce/2023/09/msg00019.html
2020-01-22
Published