CVE-2013-0110
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 · uneditednvSCPAPISvr.exe in the NVIDIA Stereoscopic 3D Driver service, as distributed with the NVIDIA driver before 307.78, and Release 310 before 311.00, on Windows, lacks " (double quote) characters in the service path, which allows local users to gain privileges via a Trojan horse program.
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 confidenceThe NVIDIA Stereoscopic 3D Driver service (nvSCPAPISvr.exe) contains a path injection vulnerability due to missing double-quote characters around the service executable path in Windows service configuration. This allows local attackers to hijack the service startup by placing a malicious executable with a predictable name in a location that gets resolved before the intended executable.
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<= 307.00= 310.00CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:S/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.
-
Verify NVIDIA Stereoscopic 3D service existsOpen Windows Services console (services.msc) or run: sc query nvSCPAPISvr. Also check Task Manager for nvSCPAPISvr.exe process.Affected if The nvSCPAPISvr service or process is present on the system.
-
Check installed NVIDIA driver versionRun: nvidia-smi or check Device Manager > Display adapters > NVIDIA GPU > Driver tab. Also check NVIDIA Control Panel > System Information.Affected if Driver version is 307.00 or lower, or exactly version 310.00.
-
Inspect service configuration for unquoted pathRun: sc qc nvSCPAPISvr (query service configuration) and examine the BINARY_PATH_NAME field. The path should show nvSCPAPISvr.exe without surrounding double quotes.Affected if The BINARY_PATH_NAME shows an unquoted path containing spaces (e.g., Program Files\NVIDIA Corporation\...) without wrapping double quotes.
-
Check for service binary locationRun: sc qc nvSCPAPISvr and note the path. Typical location: C:\Program Files\NVIDIA Corporation\nvSCPAPISvr\nvSCPAPISvr.exeAffected if Service executable path is in a directory with spaces (like Program Files) and lacks quotes in the service configuration.
-
Verify service runs with elevated privilegesRun: sc qc nvSCPAPISvr and check the START type (typically AUTO_START) and the account (often LocalSystem).Affected if Service is configured to run automatically with elevated privileges (like LocalSystem) and has an unquoted executable path.
User is affected if nvSCPAPISvr service exists, the NVIDIA driver version is 307.00 or lower or exactly 310.00, AND the service configuration shows an unquoted path in BINARY_PATH_NAME.
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 dataUpgrade NVIDIA drivers to version 307.78 or later (or Release 310 to 311.00 or later) which includes the patch for proper path quoting in the service configuration.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0110 — 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-2013-0110 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