CVE-2011-2007
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 "Endless Loop DoS in snabase.exe 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 · high confidenceA denial of service vulnerability exists in Microsoft Host Integration Server's snabase.exe component. Remote attackers can send specially crafted TCP or UDP packets to trigger an endless loop, causing 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 is installedCheck for the presence of the Host Integration Server installation directory (typically at C:\Program Files\Microsoft Host Integration Server or C:\Program Files (x86)\Microsoft Host Integration Server). Also check Add/Remove Programs for 'Microsoft Host Integration Server' entry.Affected if Host Integration Server 2004, 2006, 2009, or 2010 is listed as installed
-
Identify the installed versionOpen Add/Remove Programs (or Programs and Features) and locate the entry for Microsoft Host Integration Server. Note the exact version number displayed (e.g., 2004, 2006, 2009, or 2010).Affected if The installed version is 2004, 2006, 2009, or 2010
-
Confirm snabase.exe component existsNavigate to the Host Integration Server installation directory and verify the presence of snabase.exe file. Right-click the file and select Properties > Details to view version information.Affected if snabase.exe exists in the Host Integration Server installation folder
-
Check if SNA Server service is runningOpen Services (services.msc) and look for 'SNA Server' or 'IBM Host Integration SNA Server' service. Check if its status is Running. Also verify if the service listens on TCP/UDP ports (typically ports 1470, 1471, or 1472).Affected if The SNA Server service is running and exposed to network traffic (listening on SNA ports)
If Host Integration Server versions 2004, 2006, 2009, or 2010 are installed with the snabase.exe component and the SNA Server service is running and network-accessible, the environment is vulnerable to CVE-2011-2007.
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-2007, or upgrade to a patched version of Host Integration Server. If patching is not immediately possible, consider filtering external traffic to SNA Server ports at the network perimeter.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2007 — 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-2007 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