CVE-2023-5380
Last modified
CVE-2023-5380 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. A use-after-free flaw was found in the xorg-x11-server. An X server crash may occur in a very specific and legacy configuration (a multi-screen setup with multiple protocol screens, also known as Zaphod mode) if the pointer is warped from within a window on one screen to the root window of the other screen and if the original window is destroyed followed by another window being destroyed.. EPSS estimates a 0.71% chance of exploitation in the next 30 days.
Description
A use-after-free flaw was found in the xorg-x11-server. An X server crash may occur in a very specific and legacy configuration (a multi-screen setup with multiple protocol screens, also known as Zaphod mode) if the pointer is warped from within a window on one screen to the root window of the other screen and if the original window is destroyed followed by another window being destroyed.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| X.Org | X Server | < 21.1.9 |
| X.Org | Xwayland | < 23.2.2 |
| Redhat | Enterprise Linux | 7.0 |
| Redhat | Enterprise Linux | 8.0 |
| Redhat | Enterprise Linux | 9.0 |
| Fedoraproject | Fedora | 37 |
| Fedoraproject | Fedora | 38 |
| Fedoraproject | Fedora | 39 |
| Debian | Debian Linux | 11.0 |
| Debian | Debian Linux | 12.0 |
References
- https://access.redhat.com/errata/RHSA-2023:7428Third Party Advisory
- https://access.redhat.com/security/cve/CVE-2023-5380Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2244736Issue Tracking
- https://lists.x.org/archives/xorg-announce/2023-October/003430.htmlPatch, Vendor Advisory
- https://access.redhat.com/errata/RHSA-2023:7428Third Party Advisory
- https://access.redhat.com/security/cve/CVE-2023-5380Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2244736Issue Tracking
- https://lists.x.org/archives/xorg-announce/2023-October/003430.htmlPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-5380?
How severe is CVE-2023-5380?
How do I fix CVE-2023-5380?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53794In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2023-53795In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53796In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53797In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53798In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53799In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53800In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53801In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53802In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53803In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2023-53804In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53805Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2023-5380?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
