CVE-2019-18423
Last modified
CVE-2019-18423 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. An issue was discovered in Xen through 4.12.x allowing ARM guest OS users to cause a denial of service via a XENMEM_add_to_physmap hypercall. p2m->max_mapped_gfn is used by the functions p2m_resolve_translation_fault() and p2m_get_entry() to sanity check guest physical frame. EPSS estimates a 2.06% chance of exploitation in the next 30 days.
Description
An issue was discovered in Xen through 4.12.x allowing ARM guest OS users to cause a denial of service via a XENMEM_add_to_physmap hypercall. p2m->max_mapped_gfn is used by the functions p2m_resolve_translation_fault() and p2m_get_entry() to sanity check guest physical frame. The rest of the code in the two functions will assume that there is a valid root table and check that with BUG_ON(). The function p2m_get_root_pointer() will ignore the unused top bits of a guest physical frame. This means that the function p2m_set_entry() will alias the frame. However, p2m->max_mapped_gfn will be updated using the original frame. It would be possible to set p2m->max_mapped_gfn high enough to cover a frame that would lead p2m_get_root_pointer() to return NULL in p2m_get_entry() and p2m_resolve_translation_fault(). Additionally, the sanity check on p2m->max_mapped_gfn is off-by-one allowing "highest mapped + 1" to be considered valid. However, p2m_get_root_pointer() will return NULL. The problem could be triggered with a specially crafted hypercall XENMEM_add_to_physmap{, _batch} followed by an access to an address (via hypercall or direct access) that passes the sanity check but cause p2m_get_root_pointer() to return NULL. A malicious guest administrator may cause a hypervisor crash, resulting in a Denial of Service (DoS). Xen version 4.8 and newer are vulnerable. Only Arm systems are vulnerable. x86 systems are not affected.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Xen | Xen | >= 4.8, <= 4.12.1 |
| Debian | Debian Linux | 9.0 |
| Debian | Debian Linux | 10.0 |
| Fedoraproject | Fedora | 29 |
| Fedoraproject | Fedora | 30 |
| Fedoraproject | Fedora | 31 |
References
- http://www.openwall.com/lists/oss-security/2019/10/31/4Mailing List, Patch, Third Party Advisory
- http://xenbits.xen.org/xsa/advisory-301.htmlPatch, Vendor Advisory
- https://seclists.org/bugtraq/2020/Jan/21Mailing List, Third Party Advisory
- https://security.gentoo.org/glsa/202003-56Third Party Advisory
- https://www.debian.org/security/2020/dsa-4602Third Party Advisory
- http://www.openwall.com/lists/oss-security/2019/10/31/4Mailing List, Patch, Third Party Advisory
- http://xenbits.xen.org/xsa/advisory-301.htmlPatch, Vendor Advisory
- https://seclists.org/bugtraq/2020/Jan/21Mailing List, Third Party Advisory
- https://security.gentoo.org/glsa/202003-56Third Party Advisory
- https://www.debian.org/security/2020/dsa-4602Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-18423?
How severe is CVE-2019-18423?
How do I fix CVE-2019-18423?
Are you affected by CVE-2019-18423?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
