CVE-2011-2008
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMicrosoft Host Integration Server (HIS) 2004 SP1, 2006 SP1, 2009, and 2010 allows remote attackers to cause a denial of service (SNA Server service outage) via crafted TCP or UDP traffic, aka "Access of Unallocated Memory DoS Vulnerability."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMicrosoft Host Integration Server (HIS) contains a denial of service vulnerability in the SNA Server service. Remote attackers can send specially crafted TCP or UDP packets to the affected system, triggering an access of unallocated memory condition that causes the SNA Server service to crash and remain unavailable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2004= 2006= 2009= 2010CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Host Integration Server installationCheck for Microsoft Host Integration Server in the list of installed programs via Control Panel > Programs and Features, or query the Windows Registry at HKLM\SOFTWARE\Microsoft\Host Integration ServerAffected if Host Integration Server is listed as installed
-
Determine installed HIS versionCheck the installed version by querying the registry key HKLM\SOFTWARE\Microsoft\Host Integration Server\Setup\ProductVersion, or right-click the HIS entry in Add/Remove Programs and select PropertiesAffected if The installed version is 2004, 2006, 2009, or 2010 (any of the affected versions listed)
-
Confirm SNA Server service statusOpen Services console (services.msc) and locate the SNA Server service, or run 'sc query snaserver' from command promptAffected if The SNA Server service exists and is in a Running or Started state
-
Check network binding exposureRun 'netstat -an' and look for ports 1478, 1479, 1477 (SNA Server default ports) in LISTENING state, or check via netstat -ano | findstr LISTENINGAffected if The system is listening on SNA Server ports (1477-1479) and is accessible from untrusted networks
A user is affected if Host Integration Server versions 2004, 2006, 2009, or 2010 is installed with the SNA Server service enabled and the system is network-accessible to remote attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Microsoft security update for CVE-2011-2008, or upgrade to a newer version of Host Integration Server beyond 2010. Network segmentation and firewall rules can limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-2008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data