# CVE-2018-20176: Denial of service in n/a

> Out-of-bounds reads in rdesktop allow attackers to cause a denial of service via crafted input, affecting users of the RDP client.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-20176, DEBIAN-CVE-2018-20176, GHSA-32x7-fpgq-gpw8, UBUNTU-CVE-2018-20176

## What is CVE-2018-20176?

CVE-2018-20176 is a high-severity denial of service vulnerability in n/a, published on 15 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rdesktop versions up to and including v1.8.3 contain several Out-Of- Bounds Reads in the file secure.c that result in a Denial of Service (segfault).

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2018-20176?

It affects 1 product.


Products: Rdesktop Rdesktop.

## How do I fix CVE-2018-20176?

Upgrade to a fixed version.

## Is CVE-2018-20176 being exploited?

There is no known exploitation of CVE-2018-20176 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-20179](https://insights.sbomify.com/CVE-2018-20179/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-1801](https://insights.sbomify.com/CVE-2008-1801/): Integer overflow in n/a (critical 9.3)
- [CVE-2008-1802](https://insights.sbomify.com/CVE-2008-1802/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-1803](https://insights.sbomify.com/CVE-2008-1803/): Integer overflow in n/a (critical 9.3)
- [CVE-2019-15682](https://insights.sbomify.com/CVE-2019-15682/): Denial of service in RDesktop (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20176 and fix it if it is affected.

What it is: CVE-2018-20176 is a high-severity denial of service vulnerability in n/a, published on 15 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20176 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-20176/ (Markdown: https://insights.sbomify.com/CVE-2018-20176/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-20176
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-20176
- OSV: https://osv.dev/vulnerability/CVE-2018-20176

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-20176/
Summaries are generated and may contain mistakes; the official description above is the record.