# CVE-2010-1689: Weak cryptography in n/a

> Predictable DNS transaction IDs allow man-in-the-middle attackers to spoof DNS responses, potentially redirecting traffic or bypassing security controls.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2986-5hvv-7665

## What is CVE-2010-1689?

CVE-2010-1689 is a medium-severity vulnerability in Microsoft Exchange Server, published on 7 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The DNS implementation in smtpsvc.dll before 6.0.2600.5949 in Microsoft Windows 2000 SP4 and earlier, Windows XP SP3 and earlier, Windows Server 2003 SP2 and earlier, Windows Server 2008 SP2 and earlier, Windows Server 2008 R2, Exchange Server 2003 SP3 and earlier, Exchange Server 2007 SP2 and earlier, and Exchange Server 2010 uses predictable transaction IDs that are formed by incrementing a previous ID by 1, which makes it easier for man-in-the-middle attackers to spoof DNS responses, a different vulnerability than CVE-2010-0024 and CVE-2010-0025.

Weakness: CWE-310

## Which versions are affected by CVE-2010-1689?

It affects 5 products.


Products: Microsoft Exchange Server, Microsoft Windows 2000, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Xp.

## How do I fix CVE-2010-1689?

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

## Is CVE-2010-1689 being exploited?

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

## Other vulnerabilities in Microsoft Exchange Server

- [CVE-2024-21410](https://insights.sbomify.com/CVE-2024-21410/): Microsoft Exchange Server Privilege Escalation (critical 9.8, exploited in the wild)
- [CVE-2021-34473](https://insights.sbomify.com/CVE-2021-34473/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-26855](https://insights.sbomify.com/CVE-2021-26855/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-34523](https://insights.sbomify.com/CVE-2021-34523/): Microsoft Exchange Server Privilege Escalation (critical 9.0, exploited in the wild)
- [CVE-2023-21529](https://insights.sbomify.com/CVE-2023-21529/): Microsoft Exchange Server Deserialization of Untrusted Data (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1689 and fix it if it is affected.

What it is: CVE-2010-1689 is a medium-severity vulnerability in Microsoft Exchange Server, published on 7 May 2010. 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-2010-1689 in the wild and no public exploit code.

Affected product: Microsoft Exchange Server. 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-2010-1689/ (Markdown: https://insights.sbomify.com/CVE-2010-1689/index.md)
```

## Sources

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

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