CVE-2024-45817

In x86's APIC (Advanced Programmable Interrupt Controller) architecture, error conditions are reported in a status register. Furthermore, the OS can opt to receive an interrupt when a new error occurs. It is possible to configure the error interrupt with an illegal vector, which generates an error when an error interrupt is raised. This case causes Xen to recurse through vlapic_error(). The recursion itself is bounded; errors accumulate in the the status register and only generate an interrupt when a new status bit becomes set. However, the lock protecting this state in Xen will try to be taken recursively, and deadlock.

CVSS v3 7.3 HIGH

7.3^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 3.4

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact LOW

Integrity Impact LOW

Availability Impact LOW

Scope UNCHANGED

References

Link	Resource
https://xenbits.xenproject.org/xsa/advisory-462.html
http://www.openwall.com/lists/oss-security/2024/09/24/1
http://xenbits.xen.org/xsa/advisory-462.html

Configurations

No configuration.

History

No history.

Information

Published : 2024-09-25 11:15

Updated : 2024-11-21 09:38

NVD link : CVE-2024-45817

Mitre link : CVE-2024-45817

CVE.ORG link : CVE-2024-45817

JSON object : View

Products Affected

No product.

CWE

CWE-209

Generation of Error Message Containing Sensitive Information

{"id": "CVE-2024-45817", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 3.9}]}, "published": "2024-09-25T11:15:12.277", "references": [{"url": "https://xenbits.xenproject.org/xsa/advisory-462.html", "source": "security@xen.org"}, {"url": "http://www.openwall.com/lists/oss-security/2024/09/24/1", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://xenbits.xen.org/xsa/advisory-462.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-209"}]}], "descriptions": [{"lang": "en", "value": "In x86's APIC (Advanced Programmable Interrupt Controller) architecture,\nerror conditions are reported in a status register. Furthermore, the OS\ncan opt to receive an interrupt when a new error occurs.\n\nIt is possible to configure the error interrupt with an illegal vector,\nwhich generates an error when an error interrupt is raised.\n\nThis case causes Xen to recurse through vlapic_error(). The recursion\nitself is bounded; errors accumulate in the the status register and only\ngenerate an interrupt when a new status bit becomes set.\n\nHowever, the lock protecting this state in Xen will try to be taken\nrecursively, and deadlock."}, {"lang": "es", "value": "En la arquitectura APIC (Advanced Programmable Interrupt Controller) de x86, las condiciones de error se informan en un registro de estado. Adem\u00e1s, el sistema operativo puede optar por recibir una interrupci\u00f3n cuando se produce un nuevo error. Es posible configurar la interrupci\u00f3n de error con un vector ilegal, que genera un error cuando se genera una interrupci\u00f3n de error. Este caso hace que Xen recurra a trav\u00e9s de vlapic_error(). La recursi\u00f3n en s\u00ed est\u00e1 limitada; los errores se acumulan en el registro de estado y solo generan una interrupci\u00f3n cuando se establece un nuevo bit de estado. Sin embargo, el bloqueo que protege este estado en Xen intentar\u00e1 tomarse de forma recursiva y se producir\u00e1 un bloqueo."}], "lastModified": "2024-11-21T09:38:08.627", "sourceIdentifier": "security@xen.org"}