# CVE-2005-1794: Weak cryptography in n/a

> Remote attackers can spoof server public keys and conduct man-in-the-middle attacks due to a hardcoded RSA private key in the RDP implementation.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2005
- **Updated:** 22 May 2026
- **Also known as:** GHSA-68x9-rr6m-w8fv

## What is CVE-2005-1794?

CVE-2005-1794 is a high-severity vulnerability in n/a, published on 1 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft Terminal Server using Remote Desktop Protocol (RDP) 5.2 stores an RSA private key in mstlsapi.dll and uses it to sign a certificate, which allows remote attackers to spoof public keys of legitimate servers and conduct man-in-the-middle attacks.

## Which versions are affected by CVE-2005-1794?

It affects 2 products.


Products: Microsoft Remote Desktop Connection, Microsoft Windows Terminal Services Using Rdp.

## How do I fix CVE-2005-1794?

No fix has been published for CVE-2005-1794 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-1794 being exploited?

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

Public exploit code:

- Scanner for network for CVE-2005-1794. (github_poc): https://github.com/InitRoot/CVE-2005-1794Scanner

## Other vulnerabilities in n/a

- [CVE-2013-1296](https://insights.sbomify.com/CVE-2013-1296/): Use after free in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1794 and fix it if it is affected.

What it is: CVE-2005-1794 is a high-severity vulnerability in n/a, published on 1 Jun 2005. 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-2005-1794 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-2005-1794/ (Markdown: https://insights.sbomify.com/CVE-2005-1794/index.md)
```

## Sources

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

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