CVE-2010-0812
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 Windows XP SP2 and SP3, Server 2003 SP2, Vista Gold, SP1, and SP2, and Server 2008 Gold and SP2 allow remote attackers to bypass intended IPv4 source-address restrictions via a mismatched IPv6 source address in a tunneled ISATAP packet, aka "ISATAP IPv6 Source Address Spoofing 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 confidenceThis vulnerability in Windows XP/Server 2003/Vista/Server 2008 allows attackers to bypass IPv4 source-address restrictions by sending ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) tunneled IPv6 packets with mismatched IPv6 source addresses. The attack exploits how ISATAP tunnels IPv6 over IPv4, enabling source address spoofing that defeats ACLs based on IPv4 source filtering.
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 dataall versionsall versionsall versionsall versionsall versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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.
-
Identify Windows versionRun 'winver' or check system properties. Affected versions are Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 - all versions of these products.Affected if The system runs any version of Windows XP, Server 2003, Vista, or Server 2008.
-
Verify ISATAP is enabledCheck the ISATAP tunnel adapter status by running 'netsh interface isatap show state' or inspecting network adapters in Device Manager for 'ISATAP' tunnel adapters.Affected if ISATAP tunnel adapter is present and enabled on the system.
-
Check ISATAP router configurationRun 'netsh interface isatap show router' to see if an ISATAP router is configured. Also check registry key HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters\IsatapRouter for configured routers.Affected if An ISATAP router is configured or the system is configured to use ISATAP.
-
Inspect IPv4 source filtering rulesReview IPv4 firewall rules, IPsec policies, or network ACLs that filter based on IPv4 source addresses. Check netsh advfirewall firewall show rule all or legacy Windows Firewall settings.Affected if The system or network implements IPv4 source-based ACLs, firewall rules, or filters that could be bypassed via ISATAP tunneling.
The system is affected if it runs an affected Windows version (XP/Server 2003/Vista/Server 2008) AND has ISATAP enabled AND relies on IPv4 source address filtering that could be spoofed through ISATAP tunneled IPv6 packets.
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 dataPrimary mitigation is upgrading from these end-of-life Windows versions. For environments requiring continued support, disable ISATAP if not needed, or implement network-level filtering to validate that IPv6 source addresses in ISATAP traffic match the encapsulating IPv4 source address.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0812 — 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-2010-0812 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