CVE-2022-4283
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in X.Org. This security flaw occurs because the XkbCopyNames function left a dangling pointer to freed memory, resulting in out-of-bounds memory access on subsequent XkbGetKbdByName requests.. This issue can lead to local privileges elevation on systems where the X server is running privileged and remote code execution for ssh X forwarding sessions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA use-after-free vulnerability in X.Org's XkbCopyNames function leaves a dangling pointer to freed memory, causing out-of-bounds memory access on subsequent XkbGetKbdByName requests. This can be exploited for local privilege escalation on systems with privileged X servers or remote code execution via SSH X forwarding.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 36= 37= 6.0= 7.0= 8.0= 9.0= 11.0= 1.20.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed X.org X Server versionRun `rpm -qa | grep xorg-x11-server` (RHEL/Fedora) or `dpkg -l | grep xserver-xorg` (Debian) to list installed X server packages and their versionsAffected if The installed version matches 1.20.4 or falls within the affected ranges (RHEL 6.0-9.0, Fedora 36-37, Debian 11.0)
-
Verify X server is runningRun `ps aux | grep Xorg` or `ps aux | grep X` to check if an X server process is activeAffected if An X server is running and the version is vulnerable per step 1
-
Check if X keyboard extension (XKB) is in useInspect X server configuration: look for XKB settings in /etc/X11/xorg.conf, /etc/X11/xorg.conf.d/, or check for XKB-related files in /usr/share/X11/xkb/. Alternatively, run `setxkbmap -print` or examine X logs for XKB initializationAffected if XKB is enabled and active, since the vulnerability resides in the XkbCopyNames function
-
Inspect SSH X11 forwarding configurationCheck /etc/ssh/sshd_config for 'X11Forwarding' directive. Run `grep -i x11forwarding /etc/ssh/sshd_config`Affected if X11Forwarding is set to yes (especially on multi-user systems where unprivileged users could exploit the flaw via SSH)
-
Review X server logs for XkbGetKbdByName usageExamine /var/log/Xorg.0.log or current X logs for entries containing 'XkbGetKbdByName' or 'XkbCopyNames'Affected if These functions appear in logs, indicating the vulnerable code path is being exercised
A system is affected if it runs a vulnerable X.org X Server version (1.20.4 or affected RHEL/Debian/Fedora versions) with XKB enabled, particularly when X11 forwarding is permitted in SSH.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply available X.Org security patches or upgrade to a patched X server version. As a defense-in-depth measure, disable X11 forwarding in sshd_config or restrict it to trusted hosts until the patch is applied.
X.Org Server version newer than 1.20.4 (fixed in subsequent point releases of the xorg-x11-server package)
- 1. Identify the operating system and version running on the affected system from: Fedora 36/37, Enterprise Linux 6.0-9.0, Debian 11.0, or X Server 1.20.4
- 2. For Fedora systems: Run 'dnf update xorg-x11-server' to apply the latest security update
- 3. For Enterprise Linux systems: Run 'yum update xorg-x11-server' or 'dnf update xorg-x11-server' to apply RHSA/ALSA security patches
- 4. For Debian systems: Run 'apt-get update && apt-get upgrade xserver-xorg-core' to apply DSA security updates
- 5. After updating, restart the X server (or reboot the system) to load the corrected version
- 6. Verify the fix by checking the installed version matches a version released after the CVE publication date (December 2022)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-4283 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data