# CVE-2011-1889: Microsoft Forefront TMG Remote Code Execution

> Remote attackers can execute arbitrary code on Microsoft Forefront TMG 2010 via a memory corruption vulnerability in the firewall client.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2011
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-v7xg-xv38-f34w

## What is CVE-2011-1889?

CVE-2011-1889 is a critical memory corruption vulnerability in n/a, published on 16 Jun 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NSPLookupServiceNext function in the client in Microsoft Forefront Threat Management Gateway (TMG) 2010 allows remote attackers to execute arbitrary code via vectors involving unspecified requests, aka "TMG Firewall Client Memory Corruption Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2011-1889?

It affects 1 product.


Products: Microsoft Forefront Threat Management Gateway.

## How do I fix CVE-2011-1889?

No fix has been published for CVE-2011-1889 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2011-1889 being exploited?

Yes. Attackers have exploited CVE-2011-1889 in the wild since at least 3 Mar 2022.

## Other vulnerabilities in n/a

- [CVE-2009-0077](https://insights.sbomify.com/CVE-2009-0077/): Denial of service in n/a (medium 5.0)
- [CVE-2009-0237](https://insights.sbomify.com/CVE-2009-0237/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1889 and fix it if it is affected.

What it is: CVE-2011-1889 is a critical memory corruption vulnerability in n/a, published on 16 Jun 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2011-1889 in the wild since at least 3 Mar 2022.

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-2011-1889/ (Markdown: https://insights.sbomify.com/CVE-2011-1889/index.md)
```

## Sources

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

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