CVE-2010-3963
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 · uneditedBuffer overflow in the Routing and Remote Access NDProxy component in the kernel in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 allows local users to gain privileges via a crafted application, related to the Routing and Remote Access service (RRAS) and improper copying from user mode to the kernel, aka "Kernel NDProxy Buffer Overflow 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 confidenceBuffer overflow in Windows kernel's NDProxy component (used by Routing and Remote Access service) allows local privilege escalation via improper data copying from user mode to kernel mode, enabling attackers to execute arbitrary code with elevated privileges.
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 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 operating system versionRun 'winver' or check System Properties to confirm the Windows version. Alternatively, run 'systeminfo' from command prompt and look for OS Name and OS Version fields.Affected if The OS is not Windows XP or Windows Server 2003 (all versions of these products are affected; other versions are not)
-
Check if Routing and Remote Access (RRAS) service is enabledOpen Services (services.msc) and locate 'Routing and Remote Access' or run 'sc query RemoteAccess' from command prompt. Also check 'sc query all' to list all services.Affected if The RRAS service is running or set to Automatic startup (the vulnerability requires NDProxy, which is activated by RRAS)
-
Verify NDProxy driver is loadedRun 'driverquery | findstr NDProxy' or check the driver list in Device Manager under 'Non-Plug and Play Drivers'. The driver file is typically located at %SystemRoot%\system32\drivers\NDProxy.sys.Affected if The NDProxy.sys driver is present and loaded (this is the vulnerable component)
-
Check NDProxy driver versionRight-click on NDProxy.sys in %SystemRoot%\system32\drivers\ and select Properties, then view the Version tab. Alternatively, use 'strings' or a hex editor to examine the driver file version resources.Affected if The driver version matches the vulnerable versions present in unpatched Windows XP or Server 2003 installations (compare to Microsoft's security bulletin MS10-099)
A user is affected if they are running Windows XP or Windows Server 2003 with the RRAS service enabled and the NDProxy driver loaded, on an unpatched system.
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 Microsoft security updates for this CVE to affected Windows XP and Server 2003 systems; consider disabling RRAS if not required, or implementing least-privilege access controls to limit local attack surface.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3963 — 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-3963 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