Security readout for executives and security teams
CVE-2019-20388 is a libxml2 memory leak that can degrade service availability when XML schema stream validation is used. The public record rates it high because exploitation needs no privileges or user interaction and can affect availability, not data confidentiality or integrity. Exposure is most likely where applications or packaged products use libxml2 2.9.10 for XML schema stream validation, especially with untrusted XML input. The provided CVE data does not enumerate CPEs or complete affected product versions. Treat as high priority for systems processing untrusted XML, particularly externally reachable services. It is less urgent than proven exploited remote code execution, but availability loss can still disrupt business operations. Mitigation focus: Update libxml2 using your operating system or product vendor’s security packages.; Prioritize internet-facing services that accept or validate untrusted XML input.; Check Fedora, openSUSE, Debian, Gentoo, Oracle, and NetApp guidance where applicable..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-20388 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- FEDORA-2020-41fe1680f6CVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2020-0c71c00af4CVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2020-7694e8be73CVE reference · vendor-advisory, x_refsource_FEDORA
- https://www.oracle.com/security-alerts/cpujul2020.htmlCVE reference · x_refsource_MISC
- https://gitlab.gnome.org/GNOME/libxml2/merge_requests/68CVE reference · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20200702-0005/CVE reference · x_refsource_CONFIRM
- [debian-lts-announce] 20200909 [SECURITY] [DLA 2369-1] libxml2 security updateCVE reference · mailing-list, x_refsource_MLIST
- GLSA-202010-04CVE reference · vendor-advisory, x_refsource_GENTOO
- https://www.oracle.com/security-alerts/cpuoct2021.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpujul2022.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.