CVE-2024-31145

Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. In the logic establishing these mappings, error handling was flawed, resulting in such mappings to potentially remain in place when they should have been removed again. Respective guests would then gain access to memory regions which they aren't supposed to have access to.

CVSS v3 7.5 HIGH

7.5^/10

CVSS v3 : HIGH

Vector :

Exploitability : 0.8 / Impact : 6.0

Attack Vector LOCAL

Attack Complexity HIGH

Privileges Required HIGH

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope CHANGED

References

Link	Resource
https://xenbits.xenproject.org/xsa/advisory-460.html
http://www.openwall.com/lists/oss-security/2024/08/14/2
http://xenbits.xen.org/xsa/advisory-460.html

Configurations

No configuration.

History

No history.

Information

Published : 2024-09-25 11:15

Updated : 2024-11-21 09:12

NVD link : CVE-2024-31145

Mitre link : CVE-2024-31145

CVE.ORG link : CVE-2024-31145

JSON object : View

Products Affected

No product.

CWE

CWE-400

Uncontrolled Resource Consumption

{"id": "CVE-2024-31145", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 0.8}]}, "published": "2024-09-25T11:15:12.133", "references": [{"url": "https://xenbits.xenproject.org/xsa/advisory-460.html", "source": "security@xen.org"}, {"url": "http://www.openwall.com/lists/oss-security/2024/08/14/2", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://xenbits.xen.org/xsa/advisory-460.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-400"}]}], "descriptions": [{"lang": "en", "value": "Certain PCI devices in a system might be assigned Reserved Memory\nRegions (specified via Reserved Memory Region Reporting, \"RMRR\") for\nIntel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used\nfor platform tasks such as legacy USB emulation.\n\nSince the precise purpose of these regions is unknown, once a device\nassociated with such a region is active, the mappings of these regions\nneed to remain continuouly accessible by the device. In the logic\nestablishing these mappings, error handling was flawed, resulting in\nsuch mappings to potentially remain in place when they should have been\nremoved again. Respective guests would then gain access to memory\nregions which they aren't supposed to have access to."}, {"lang": "es", "value": "Ciertos dispositivos PCI de un sistema se les pueden asignar regiones de memoria reservadas (especificadas a trav\u00e9s de informes de regiones de memoria reservadas, \"RMRR\") para Intel VT-d o rangos de mapeo de Unity para AMD-Vi. Por lo general, se utilizan para tareas de plataforma como la emulaci\u00f3n USB heredada. Dado que se desconoce el prop\u00f3sito preciso de estas regiones, una vez que un dispositivo asociado con dicha regi\u00f3n est\u00e1 activo, las asignaciones de estas regiones deben permanecer accesibles continuamente para el dispositivo. En la l\u00f3gica que establece estas asignaciones, el manejo de errores era defectuoso, lo que result\u00f3 en que dichas asignaciones potencialmente permanecieran en su lugar cuando deber\u00edan haberse eliminado nuevamente. Los invitados respectivos obtendr\u00edan entonces acceso a regiones de memoria a las que se supone que no deber\u00edan tener acceso."}], "lastModified": "2024-11-21T09:12:55.410", "sourceIdentifier": "security@xen.org"}