Skip to content
Fencer Vulns
critical 9.3

CVE-2008-1803 json

Integer signedness error in the xrealloc function (rdesktop.c) in RDesktop 1.5.0 allows remote attackers to execute arbitrary code via unkn…

published 2008-05-12 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1803

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.7%
EPSS 6.7% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

Integer signedness error in the xrealloc function (rdesktop.c) in RDesktop 1.5.0 allows remote attackers to execute arbitrary code via unknown parameters that trigger a heap-based overflow. NOTE: the role of the channel_process function was not specified by the original researcher.

Patch / fix

  • rdesktop Debian 14, Debian 13, Debian 12 1.5.0-4+cvs20071006

debian advisories DEBIAN-CVE-2008-1803

  • rdesktop RHEL 5 1.4.1-6

red hat advisories RHSA-2008:0575

  • rdesktop openSUSE Tumbleweed 1.9.0-4.6

opensuse advisories openSUSE-SU-2024:11298-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2008-1803 updated cvss 5.4

rdesktop: channel_process() Integer Signedness Vulnerability

  • Red Hat Enterprise Linux (v. 5 server) rdesktop 1.4.1-6 Red Hat Enterprise Linux Desktop (v. 5 client) rdesktop 1.4.1-6
    fixed: vendor fix RHSA-2008:0575

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.74% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • rdesktop.cvs.sourceforge.net http://rdesktop.cvs.sourceforge.net/rdesktop/rdesktop/rdesktop.c?r1=1.161&r2=1.162&pathrev=HEAD referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.