Debian LinuxOperating system · Debian
CVE-2017-2835
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 · uneditedAn exploitable code execution vulnerability exists in the RDP receive functionality of FreeRDP 2.0.0-beta1+android11. A specially crafted server response can cause an out-of-bounds write resulting in an exploitable condition. An attacker can compromise the server or use a man in the middle to trigger this vulnerability.
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 confidenceAn out-of-bounds write vulnerability exists in FreeRDP 2.0.0-beta1+android11's RDP receive functionality. When processing specially crafted server responses, the client performs an out-of-bounds memory write that can be leveraged for remote code execution. The attacker requires either a compromised RDP server or a man-in-the-middle position.
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
= 8.0= 9.0= 2.0.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check if FreeRDP is installedRun 'dpkg -l | grep freerdp' on Debian systems, or 'rpm -qa | grep freerdp' on RHEL-based systems, or 'which xfreerdp' to find the client binaryAffected if FreeRDP package or binary is present on the system
-
Identify the installed FreeRDP versionRun 'dpkg -l freerdp' or 'freerdp-version' command, or check the binary version with 'xfreerdp --version'Affected if The version displayed is exactly 2.0.0
-
Confirm the operating system versionRun 'cat /etc/debian_version' to check if the system is Debian 8.0 or 9.0Affected if The system is running Debian 8.0 or 9.0
-
Determine if RDP client connections are being usedReview any scripts, cron jobs, or user activity that invokes freerdp or xfreerdp to connect to RDP serversAffected if FreeRDP is actively used or configured to connect to remote RDP servers
A system is affected if FreeRDP version 2.0.0 is installed and actively used (or configured) to make RDP connections, especially in environments where the server may be untrusted or on shared networks where MITM is possible.
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.
From vendor dataUpdate FreeRDP to the latest patched version. As a defense-in-depth measure, enforce TLS encryption and proper certificate validation on RDP connections to prevent MITM attacks.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2835 — 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-2017-2835 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