CVE-2010-3199
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 · uneditedUntrusted search path vulnerability in TortoiseSVN 1.6.10, Build 19898 and earlier allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse dwmapi.dll that is located in the same folder as a file that is processed by Tortoise. NOTE: this is only a vulnerability when a file extension is associated with TortoiseProc or TortoiseMerge, which is not the default.
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 confidenceDLL hijacking vulnerability in TortoiseSVN 1.6.10 and earlier allows arbitrary code execution when the application loads a malicious dwmapi.dll from the same directory as a file being processed. TortoiseSVN searches the file's directory for DLLs before system paths, enabling attackers to plant Trojan horse DLLs that execute with TortoiseSVN's 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 data<= 1.6.10= 0.1= 0.2= 0.3= 0.4= 0.5= 0.5.1= 0.6= 0.6.1= 0.7= 0.8= 0.8.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Check installed TortoiseSVN versionOpen TortoiseSVN Settings > About, or run 'TortoiseProc.exe /version' from command line, or check registry key HKLM\SOFTWARE\TortoiseSVN\VersionAffected if Version is 1.6.10 or earlier, or falls within versions 0.1 through 0.8.1
-
Locate TortoiseSVN executable pathFind TortoiseSVN installation directory (commonly C:\Program Files\TortoiseSVN\) and note the TortoiseProc.exe locationAffected if Executable exists in a directory writable by other users, allowing them to place a malicious DLL alongside it
-
Check for dwmapi.dll in accessible directoriesSearch for dwmapi.dll files in user-writable directories such as user home folders, project directories, or download folders that TortoiseSVN might access when processing filesAffected if A dwmapi.dll file exists in any directory that TortoiseSVN loads files from, as the application may load it before the system DLL
-
Verify DLL search order behaviorReview any logs or test DLL loading by placing a test dwmapi.dll in a directory with a file, then opening that file with TortoiseSVN (e.g., right-click > TortoiseSVN actions)Affected if TortoiseSVN loads DLLs from the current file's directory before system paths, indicating the vulnerable behavior is present
You are affected if your TortoiseSVN version is 1.6.10 or earlier and an untrusted dwmapi.dll exists in any directory where you use TortoiseSVN to process files.
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.
dbcve · scopedEnsure file extensions are not associated with TortoiseProc or TortoiseMerge (not the default), or update to a patched version of TortoiseSVN that loads DLLs only from secure system paths.
TortoiseSVN 1.6.11 or later (preferably latest stable 1.14.x or newer)
- 1. Download the latest version of TortoiseSVN from the official website (tortoisesvn.net) or the project's official repository
- 2. Uninstall the current vulnerable version of TortoiseSVN (1.6.10 or earlier)
- 3. Install the latest stable version of TortoiseSVN
- 4. Verify the installation by checking the version number in the TortoiseSVN settings or about dialog
- 5. Ensure that file associations are configured appropriately if using TortoiseProc or TortoiseMerge
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3199 — 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-3199 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