libyang: double-free in yyparse() when organization field is not terminated
Published Jan 22, 2020
8.8
HIGHCVSS 3.1
EPSS 2.51%
Description
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an organization field is not terminated. 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 products
No data.
- 0.11
- 0.11
- 0.12
- 0.12
- 0.13
- 0.13
- 0.14
- 0.15
- 0.16
- 0.16
- 0.16
No data.
Red Hat Enterprise Linux 8
libyang-0:1.0.184-1.el8
Fixed · RHEA-2021:1906
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | libyang-0:1.0.184-1.el8 | Fixed | RHEA-2021:1906 |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
1 other source (Red Hat) ▾
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
No CVSS v3.0 score for this CVE.
AV:N/AC:M/Au:N/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 3, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Table of values (18 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 3, 2026 | 2.51% (0.02510) | 84.23th | v5 (v2026.06.15) |
| Jun 15, 2026 | 2.49% (0.02488) | 82.50th | v5 (v2026.06.15) |
| Mar 30, 2025 | 0.40% (0.00398) | 57.68th | v4 (v2025.03.14) |
| Mar 29, 2025 | 1.65% (0.01646) | 70.49th | v4 (v2025.03.14) |
| Mar 17, 2025 | 0.31% (0.00314) | 52.33th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.41% (0.00411) | 74.75th | v3 (v2023.03.01) |
| Feb 8, 2024 | 0.34% (0.00336) | 70.48th | v3 (v2023.03.01) |
| Nov 26, 2023 | 0.33% (0.00332) | 67.98th | v3 (v2023.03.01) |
| Nov 11, 2023 | 0.34% (0.00343) | 68.32th | v3 (v2023.03.01) |
| Sep 20, 2023 | 0.33% (0.00327) | 67.31th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.35% (0.00350) | 67.34th | v3 (v2023.03.01) |
| Mar 6, 2023 | 2.51% (0.02509) | 81.86th | v2 (v2022.01.01) |
| Apr 1, 2022 | 2.51% (0.02509) | 80.08th | v2 (v2022.01.01) |
| Feb 4, 2022 | 23.33% (0.23331) | 94.71th | v2 (v2022.01.01) |
| Feb 3, 2022 | 7.67% (0.07673) | 84.22th | v1 |
| Jan 6, 2022 | 7.67% (0.07673) | 84.07th | v1 |
| Jan 5, 2022 | 1.82% (0.01819) | 75.45th | v5 (v2026.06.15) |
| Apr 14, 2021 | 1.82% (0.01819) | 0.00th | v1 |
References (8)
- https://access.redhat.com/security/cve/CVE-2019-20397 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1793928 Issue TrackingPatchThird Party Advisory
- https://github.com/CESNET/libyang/commit/88bd6c548ba79bce176cd875e9b56e7e0ef4d8d4 PatchThird Party Advisory
- https://github.com/CESNET/libyang/compare/v0.16-r3...v1.0-r1 Third Party Advisory
- https://github.com/CESNET/libyang/issues/739 Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2023/09/msg00019.html mailing-list
- https://nvd.nist.gov/vuln/detail/CVE-2019-20397
- https://www.cve.org/CVERecord?id=CVE-2019-20397
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2019-20397 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1793928 | Issue TrackingPatchThird Party Advisory | |
| https://github.com/CESNET/libyang/commit/88bd6c548ba79bce176cd875e9b56e7e0ef4d8d4 | PatchThird Party Advisory | |
| https://github.com/CESNET/libyang/compare/v0.16-r3...v1.0-r1 | Third Party Advisory | |
| https://github.com/CESNET/libyang/issues/739 | Third Party Advisory | |
| https://lists.debian.org/debian-lts-announce/2023/09/msg00019.html | mailing-list | |
| https://nvd.nist.gov/vuln/detail/CVE-2019-20397 | ||
| https://www.cve.org/CVERecord?id=CVE-2019-20397 |
Change history (0)
No recorded changes yet.