LiveActive security incident?Get immediate response
CVE Record

CVE-2011-1889: The NSPLookupServiceNext function in the client in Microsoft Forefront Threat Management Gateway (TMG) 2010...

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."

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical remote code execution flaw in the Microsoft Forefront TMG 2010 client. A remote attacker could potentially run code through unspecified requests. CISA KEV marks it as known exploited, so any remaining deployments deserve urgent attention.

Executive priority

Treat this as urgent legacy-risk cleanup. Known exploitation plus unauthenticated remote code execution means any remaining affected client could become a direct compromise path.

Technical view

CVE-2011-1889 is a CWE-119 memory corruption issue in the NSPLookupServiceNext function of the Microsoft Forefront TMG 2010 client. The supplied CVSS 3.1 score is 9.8, with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is likely limited to environments that still have the Microsoft Forefront TMG 2010 Firewall Client installed. The structured affected-products data is incomplete, so inventory should key off the Microsoft advisory and local software records.

Exploitation context

CISA KEV status supports known exploitation. The provided sources do not describe exploit mechanics, public exploit availability, campaigns, or precise request vectors, so defenders should avoid assuming only theoretical risk.

Researcher notes

The source bundle confirms the vulnerable function, RCE impact, CWE category, CVSS vector, Microsoft bulletin, OVAL detection reference, and KEV status. It does not provide detailed affected version ranges, exploit indicators, or a non-patch workaround.

Mitigation direction

  • Apply the Microsoft MS11-040 security update where applicable.
  • Inventory systems for Forefront TMG 2010 Firewall Client installations.
  • Prioritize internet-facing or broadly reachable client systems first.
  • Check current Microsoft guidance for unsupported or legacy deployments.
  • Remove obsolete TMG client components where business use no longer exists.

Validation and detection

  • Verify whether Forefront TMG 2010 Firewall Client exists in endpoint inventory.
  • Confirm MS11-040 remediation status on identified systems.
  • Use the referenced OVAL definition or trusted scanners for detection.
  • Review vulnerability management records for CVE-2011-1889 closure.
  • Document exceptions with compensating controls and business owner approval.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-119: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2011-1889 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2011-1889Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.