CVE-2010-3397
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 PGP Desktop 9.9.0 Build 397, 9.10.x, 10.0.0 Build 2732, and probably other versions allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse tsp.dll or tvttsp.dll that is located in the same folder as a .p12, .pem, .pgp, .prk, .prvkr, .pubkr, .rnd, or .skr file.
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 confidencePGP Desktop contains an untrusted search path vulnerability where the application loads DLL files (specifically tsp.dll or tvttsp.dll) from the same directory as certificate/key files (.p12, .pem, .pgp, .prk, .prvkr, .pubkr, .rnd, .skr) being opened. Attackers can place malicious DLLs in folders containing these file types, causing arbitrary code execution when users open the files.
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= 9.9.0= 9.10.0= 10.0.0CVSS 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.
-
Identify PGP Desktop versionCheck the installed version via Add/Remove Programs, or look in the program directory for version information (often in About or Help menu of the application)Affected if The installed version is 9.9.0, 9.10.0, or 10.0.0 exactly
-
Locate PGP key and certificate filesSearch the filesystem for files with extensions .p12, .pem, .pgp, .prk, .prvkr, .pubkr, .rnd, or .skr - these are the file types that trigger the vulnerable DLL loadingAffected if You have any of these PGP-related files stored on the system
-
Check for suspicious DLLs in key file directoriesIn each directory containing PGP key/certificate files, look for files named tsp.dll or tvttsp.dllAffected if A tsp.dll or tvttsp.dll file exists in the same folder as any of the vulnerable file types (.p12, .pem, .pgp, .prk, .prvkr, .pubkr, .rnd, .skr)
-
Verify file association with PGP DesktopCheck if PGP Desktop is registered as the default handler for .p12, .pem, .pgp, .skr, or other PGP key file extensions (via Right-click > Open With or Default Programs)Affected if PGP Desktop opens these file types and the version is one of the affected versions (9.9.0, 9.10.0, 10.0.0)
You are affected if PGP Desktop version 9.9.0, 9.10.0, or 10.0.0 is installed and a tsp.dll or tvttsp.dll file exists in any directory containing PGP key or certificate files that you open with PGP Desktop.
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 dataEnsure PGP Desktop is patched to the latest version. Avoid opening certificate and key files from untrusted or shared network locations. Remove any suspicious tsp.dll or tvttsp.dll files found in directories containing PGP key files.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3397 — 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-3397 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