CVE-2010-3965
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 Windows Media Encoder 9 on Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, and Windows Server 2008 Gold and SP2 allows local users to gain privileges via a Trojan horse DLL in the current working directory, as demonstrated by a directory that contains a Windows Media Profile (PRX) file, aka "Insecure Library Loading 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 confidenceWindows Media Encoder 9 contains an insecure library loading vulnerability where the application loads DLLs from the current working directory without validation. An attacker can place a malicious DLL (trojan horse) in a directory containing a Windows Media Profile (PRX) file; when the application opens the PRX file, it also loads the attacker's DLL, enabling local privilege escalation.
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_seriesCVSS 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.
-
Verify Windows Media Encoder 9 is installedSearch the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Windows Media Encoder 9, or check if wmenc.exe exists in Program FilesAffected if The application is present on the system
-
Confirm the exact version is 9 or 9_seriesRight-click on wmenc.exe, select Properties, and examine the File Version field under the Details tabAffected if Version equals 9 or begins with 9_series (e.g., 9.00.00.0000)
-
Identify the DLL loading vulnerability conditionThe vulnerability is inherent to the application: it loads DLLs from the current working directory when opening PRX files. No special feature needs to be enabled - this is the default insecure behavior.Affected if The software is installed and can be used to open Media Profile (PRX) files
Your system is affected if Windows Media Encoder version 9 or 9_series is installed and users can open PRX files from directories that may contain untrusted DLLs
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 · scopedRemove Windows Media Encoder 9 from vulnerable systems, or ensure users never open media files from untrusted directories. Implement the SafeDllSearchMode registry setting to change the DLL search order.
Windows Media Encoder 9 reached end of life; consider migrating to modern media encoding solutions as no direct upgrade path exists
- Apply Microsoft security update MS10-070 if available for the specific Windows version
- Enable 'Safe DLL Search Mode' via registry: Set HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SafeDllSearchMode to 1
- Alternatively, run Windows Media Encoder 9 from a trusted directory (e.g., Program Files) rather than untrusted directories containing PRX files
- Ensure the current working directory does not contain untrusted media files when launching the application
- Apply all subsequent Windows security updates to maintain protection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3965 — 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-3965 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