dbcve.org
Design Review 2011Application · Autodesk

CVE-2010-5226

MEDIUM · 6.9 CVSS v2.0 Published 2012-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Multiple untrusted search path vulnerabilities in Autodesk Design Review 2011 11.0.0.86 allow local users to gain privileges via a Trojan horse (1) dwmapi.dll, (2) whiptk_wt.7.12.601.dll, or (3) xaml_wt.7.6.0.dll file in the current working directory, as demonstrated by a directory that contains a .dwf file. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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 · low confidence

Untrusted search path vulnerability in Autodesk Design Review 2011 allows DLL hijacking. The application loads DLL files (dwmapi.dll, whiptk_wt.7.12.601.dll, xaml_wt.7.6.0.dll) from the current working directory without validating the path, enabling a local attacker to place malicious DLLs in directories containing .dwf files to achieve privilege escalation when users open those files.

MitigationUsers should avoid opening .dwf files from untrusted or shared directories. The vendor should implement secure DLL loading by using full absolute paths, whitelisting allowed DLL locations, or using DLL search path elimination APIs to prevent loading from the current working directory.

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
Design Review 2011Application
Affected:= 11.0.0.86

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of Autodesk Design Review
    Check the application version through Windows Add/Remove Programs, or right-click the application executable in Program Files and view Properties, or run 'wmic product where "name like '%Autodesk Design Review%'" get version'
    Affected if The installed version matches 11.0.0.86 (Autodesk Design Review 2011)
  2. Locate dwmapi.dll, whiptk_wt.7.12.601.dll, xaml_wt.7.6.0.dll
    Search for these specific DLL files in directories where .dwf files are commonly stored, such as user document folders, shared network drives, or download directories
    Affected if Any of these DLLs exist in directories containing .dwf files but are not the legitimate system DLLs
  3. Check application DLL loading behavior
    Use Process Monitor or similar tooling to trace DLL loads when opening a .dwf file; look for DLL loads from the current working directory rather than the application directory
    Affected if The application loads any of the target DLLs (dwmapi.dll, whiptk_wt.7.12.601.dll, xaml_wt.7.6.0.dll) from the directory where the .dwf file is located
  4. Verify .dwf file association
    Right-click a .dwf file, select Properties, and check the 'Opens with' field to confirm it is associated with Autodesk Design Review
    Affected if Autodesk Design Review 2011 is the default handler for .dwf files

You are affected if Autodesk Design Review 2011 version 11.0.0.86 is installed and you open .dwf files from directories containing the vulnerable DLLs (dwmapi.dll, whiptk_wt.7.12.601.dll, xaml_wt.7.6.0.dll).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should avoid opening .dwf files from untrusted or shared directories. The vendor should implement secure DLL loading by using full absolute paths, whitelisting allowed DLL locations, or using DLL search path elimination APIs to prevent loading from the current working directory.

Fix this in Design Review 2011 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-5226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-5226 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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