Debian LinuxOperating system · Debian

CVE-2022-23493

CRITICAL · 9.1 CVSS v3.1 Published 2022-12-09
Fix available
A fix is available. Upgrade to 0.9.21 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
xrdp 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 Out of Bound Read in xrdp_mm_trans_process_drdynvc_channel_close() 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 confidence

xrdp versions prior to 0.9.21 contain an out-of-bounds read vulnerability in the xrdp_mm_trans_process_drdynvc_channel_close() function. This memory safety flaw could allow an attacker to read sensitive memory contents or cause a denial of service. The vulnerability is in the dynamic virtual channel (drdynvc) processing code used for RDP communications.

MitigationUpgrade xrdp to version 0.9.21 or later. No workarounds are available for this issue.

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
Affected:= 11.0
XrdpApplication
Affected:< 0.9.21

CVSS 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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed xrdp version
    Run 'xrdp --version' or check the package manager (e.g., 'dpkg -l xrdp' on Debian, 'rpm -qi xrdp' on RHEL-based systems)
    Affected if The version shown is less than 0.9.21 or the version cannot be determined (indicating an older release)
  2. Identify if drdynvc module is loaded or configured
    Examine xrdp configuration files (typically /etc/xrdp/xrdp.ini or /etc/xrdp/startwm.sh) for references to drdynvc or dynamic virtual channel settings
    Affected if drdynvc or dynamic virtual channel support is explicitly enabled in the configuration
  3. Verify xrdp service is active and accepting connections
    Run 'systemctl status xrdp' or check running processes with 'ps aux | grep xrdp' to confirm the service is running
    Affected if xrdp daemon is running and the vulnerable code path is active
  4. Check for xrdp binaries and library files
    Locate xrdp installation files via 'which xrdp' and 'find /usr -name "*xrdp*" 2>/dev/null' to confirm the installation path
    Affected if The binary or library files exist, indicating an active xrdp installation with the vulnerable component present

You are affected if xrdp version is prior to 0.9.21 and the drdynvc (dynamic virtual channel) feature is enabled or in use for RDP connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.9.21 or later
Fixed in 0.9.21
Interim mitigation

Upgrade xrdp to version 0.9.21 or later. No workarounds are available for this issue.

Recommended fix High confidence

xrdp v0.9.21 or later

  1. Check current xrdp version: `xrdp --version` or `dpkg -l | grep xrdp`
  2. Update package lists: `apt update`
  3. Upgrade xrdp to version 0.9.21 or later: `apt install xrdp` or `apt upgrade xrdp`
  4. Verify the installed version matches the fixed release (0.9.21 or higher)

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23493 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23493 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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