VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

rdesktop: vulnerability history, versions and safety

rdesktop is a package in the Debian ecosystem. Vulert records 29 vulnerabilities for it across 4 affected ranges, from May 2008 to Oct 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
29 vulnerabilities recorded U29
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rdesktop vulnerabilities

Vulert verdict on rdesktop i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 30 Oct 2019. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 29 vulnerabilities on record across 11 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 29 over 11 years · 0 in the last year i
  • Latest disclosure 30 Oct 2019 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 1.8.6-1 (exclusive) 2
up to 1.8.4-1 (exclusive) 19
up to 1.7.0-1 (exclusive) 2
up to 1.5.0-4+cvs20071006 (exclusive) 6

02 Disclosure history

How often vulnerabilities are recorded

  • 2008 6
  • 2011 2
  • 2019 21

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 29 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rdesktop

The 5 most severe of 29 vulnerabilities recorded for this package

Search all 29 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Out-of-Bound Access Vulnerabilities in RDesktop - Denial of Service Risk 7.5 high 1.8.6-1 30 Oct 2019
Directory Traversal Vulnerability in rdesktop N/A unrated 1.7.0-1 24 May 2011
Critical Out-of-Bound Access Vulnerability in RDesktop Package N/A unrated 1.8.6-1 30 Oct 2019
Heap-Based Buffer Overflow Vulnerability in rdesktop Package N/A unrated 1.8.4-1 05 Feb 2019
Out-Of-Bounds Read Vulnerability in rdesktop Package N/A unrated 1.8.4-1 05 Feb 2019

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About rdesktop

Is rdesktop safe to use?

Vulert records 29 vulnerabilities for rdesktop in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 29 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does rdesktop have?

29 vulnerabilities are recorded for rdesktop in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 29 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rdesktop vulnerabilities disclosed?

0 vulnerabilities were recorded for rdesktop in the last 12 months, and the oldest entry in this database dates to 12 May 2008. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rdesktop are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rdesktop for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rdesktop version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.