Debian LinuxOperating system · Debian

CVE-2022-23483

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 libxrdp_send_to_channel() 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 · moderate confidence

xrdp versions prior to 0.9.21 contain an out-of-bounds read vulnerability in the libxrdp_send_to_channel() function. This memory disclosure flaw in the RDP channel handling code could allow an unauthenticated remote attacker to read sensitive memory contents, potentially leading to information disclosure or further exploitation.

MitigationUpgrade xrdp to version 0.9.21 or later. No workarounds exist for this vulnerability; immediate patching is recommended given the critical (9.1) severity rating.

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. Check if xrdp is installed
    Run 'dpkg -l | grep xrdp' on Debian/Ubuntu, or 'rpm -q xrdp' on RHEL/CentOS, or check for the binary at /usr/sbin/xrdp
    Affected if xrdp package or binary is present on the system
  2. Determine installed xrdp version
    Run 'xrdp --version' or 'dpkg -l xrdp' (Debian) or 'rpm -qi xrdp' (RHEL) to obtain the exact version number
    Affected if version is lower than 0.9.21
  3. Verify if xrdp service is running
    Run 'systemctl status xrdp' or 'ps aux | grep xrdp' to check if the xrdp service process is active
    Affected if the xrdp daemon is running and accepting connections
  4. Check network exposure
    Run 'ss -tlnp | grep 3389' or 'netstat -tlnp | grep 3389' to verify if port 3389 (RDP) is listening
    Affected if port 3389 is open and listening, making the service remotely accessible

A system is affected if xrdp version is below 0.9.21 AND the xrdp service is running and exposed on the network.

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 exist for this vulnerability; immediate patching is recommended given the critical (9.1) severity rating.

Recommended fix High confidence

xrdp v0.9.21 or later

  1. 1. Check current installed xrdp version: dpkg -l | grep xrdp
  2. 2. For Debian 11.0 systems, update package lists: apt-get update
  3. 3. Upgrade xrdp to version 0.9.21 or later: apt-get install xrdp (or apt-get upgrade xrdp)
  4. 4. Verify the installed version matches the security fix: dpkg -l | grep xrdp
  5. 5. Restart xrdp service if running: systemctl restart xrdp or service xrdp restart
  6. 6. Verify the service is running properly: 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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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