CVE-2011-1889
Microsoft Forefront TMG Remote Code Execution Vulnerability
Microsoft Forefront Threat Management Gateway (TMG)
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."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 49%, which is higher than 98.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2011-1889 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2011-1889.
What does CVE-2011-1889 affect?
CVE-2011-1889 affects Microsoft Forefront Threat Management Gateway (TMG). 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."
How severe is CVE-2011-1889?
CVE-2011-1889 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 49%, higher than 98.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 March 2022.
How should organisations respond to CVE-2011-1889?
Apply the vendor patch for Microsoft Forefront Threat Management Gateway (TMG) as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.