CVE-2024-31080

{"id": "CVE-2024-31080", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.5, "exploitabilityScore": 1.8}]}, "published": "2024-04-04T14:15:10.330", "references": [{"url": "https://access.redhat.com/errata/RHSA-2024:1785", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2036", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2037", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2038", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2039", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2040", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2041", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2042", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2080", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2616", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3258", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3261", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3343", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:9093", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2024:9122", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2025:12751", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/security/cve/CVE-2024-31080", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2271997", "source": "secalert@redhat.com"}, {"url": "http://www.openwall.com/lists/oss-security/2024/04/03/13", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.openwall.com/lists/oss-security/2024/04/12/10", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:1785", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2036", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2037", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2038", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2039", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2040", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2041", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2042", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2080", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:2616", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3258", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3261", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2024:3343", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/security/cve/CVE-2024-31080", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2271997", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.debian.org/debian-lts-announce/2024/04/msg00009.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6TF7FZXOKHIKPZXYIMSQXKVH7WITKV3V/", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EBLQJIAXEDMEGRGZMSH7CWUJHSVKUWLV/", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P73U4DAAWLFZAPD75GLXTGMSTTQWW5AP/", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-126"}]}], "descriptions": [{"lang": "en", "value": "A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIGetSelectedEvents() function. This issue occurs when byte-swapped length values are used in replies, potentially leading to memory leakage and segmentation faults, particularly when triggered by a client with a different endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory values and then transmit them back to the client until encountering an unmapped page, resulting in a crash. Despite the attacker's inability to control the specific memory copied into the replies, the small length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds reads."}, {"lang": "es", "value": "Se encontr\u00f3 una vulnerabilidad de sobrelectura del b\u00fafer basado en mont\u00f3n en la funci\u00f3n ProcXIGetSelectedEvents() del servidor X.org. Este problema se produce cuando se utilizan valores de longitud de bytes intercambiados en las respuestas, lo que puede provocar p\u00e9rdidas de memoria y errores de segmentaci\u00f3n, especialmente cuando lo activa un cliente con una endianidad diferente. Un atacante podr\u00eda aprovechar esta vulnerabilidad para hacer que el servidor X lea los valores de la memoria din\u00e1mica y luego los transmita de vuelta al cliente hasta encontrar una p\u00e1gina no asignada, lo que provocar\u00eda un bloqueo. A pesar de la incapacidad del atacante para controlar la memoria espec\u00edfica copiada en las respuestas, los peque\u00f1os valores de longitud que normalmente se almacenan en un entero de 32 bits pueden dar como resultado importantes intentos de lecturas fuera de los l\u00edmites."}], "lastModified": "2025-08-04T21:15:28.873", "sourceIdentifier": "secalert@redhat.com"}