Debian LinuxOperating system · Debian
CVE-2022-23479
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 · uneditedxrdp is an open source project which provides a graphical login to remote machines using Microsoft Remote Desktop Protocol (RDP). xrdp < v0.9.21 contain a buffer over flow in xrdp_mm_chan_data_in() function. There are no known workarounds for this issue. Users are advised to upgrade.
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 confidencexrdp versions before v0.9.21 contain a buffer overflow vulnerability in the xrdp_mm_chan_data_in() function, which handles incoming channel data for RDP connections. This memory corruption flaw in the remote desktop service could allow unauthenticated attackers to execute arbitrary code or cause denial of service.
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
Debian LinuxOperating system
= 11.0< 0.9.21CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if xrdp is installedRun 'dpkg -l xrdp' on Debian-based systems or 'rpm -qa | grep xrdp' on RHEL-based systems to check if the xrdp package is presentAffected if xrdp package is found installed on the system
-
Determine the installed xrdp versionRun 'dpkg -l xrdp' or 'rpm -q xrdp' to retrieve the installed version number, or check the xrdp daemon version with 'xrdp -v' if availableAffected if The displayed version is lower than 0.9.21 or the version cannot be determined (may indicate an older release)
-
Verify the xrdp service is enabled and runningRun 'systemctl status xrdp' or check if port 3389 is listening with 'ss -tlnp | grep 3389' or 'netstat -tlnp | grep 3389'Affected if The xrdp service is active and listening for RDP connections, making the vulnerability reachable over the network
-
Confirm the channel data feature is in useThe vulnerability exists in xrdp_mm_chan_data_in() which handles incoming channel data for RDP sessions. Any active RDP connection or session using channel data would trigger the vulnerable code path. Check if remote desktop connections are permitted via '/etc/xrdp/xrdp.ini' configurationAffected if RDP connections are allowed and the xrdp service is exposed to network traffic
A system is affected if xrdp is installed with a version lower than 0.9.21 and the service is running and accessible for incoming RDP connections.
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 · scoped0.9.21
Upgrade xrdp to version 0.9.21 or later. There are no known workarounds; immediate patching is required given the critical CVSS score and network-exposed attack surface.
xrdp v0.9.21 or later
- Check current installed xrdp version: dpkg -l | grep xrdp or xrdp -version
- Update package repository: apt-get update
- Upgrade xrdp package: apt-get install --only-upgrade xrdp
- Verify the installed version matches or exceeds v0.9.21: xrdp -version
- Restart xrdp service if needed: systemctl restart xrdp or service xrdp restart
- Verify the service is running: systemctl status xrdp
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23479 — 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-23479 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