CVE-2019-7365
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 · uneditedDLL preloading vulnerability in Autodesk Desktop Application versions 7.0.16.29 and earlier. An attacker may trick a user into downloading a malicious DLL file into the working directory, which may then leverage a DLL preloading vulnerability and execute code on the system.
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 confidenceA DLL preloading vulnerability exists in Autodesk Desktop Application versions 7.0.16.29 and earlier. An attacker can trick a user into downloading a malicious DLL file into the application's working directory, causing the application to load the malicious DLL instead of the legitimate one, resulting in arbitrary code execution with the user'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<= 7.0.16.29CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate Autodesk Desktop Application installationOpen the Windows Control Panel, go to Programs and Features, and look for 'Autodesk Desktop Application' in the list of installed programs. Alternatively, check common installation paths such as C:\Program Files\Autodesk\ or C:\Users\%username%\AppData\Local\Autodesk\ for the application executable.Affected if Autodesk Desktop Application is not found, the vulnerability does not apply.
-
Determine installed versionRight-click the Autodesk Desktop Application executable (typically named AutodeskDesktopApp.exe), select Properties, and view the Details tab to see the File Version. If uninstalled, run 'wmic product get name,version' or check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Autodesk entries.Affected if The version is 7.0.16.29 or earlier.
-
Inspect application directory for untrusted DLL filesNavigate to the directory where AutodeskDesktopApp.exe is installed. List all .dll files in that folder and examine whether any DLL files exist that were not shipped with the original installation or appear suspicious/unfamiliar.Affected if Unexpected or untrusted DLL files are present in the application directory.
-
Check Safe DLL Search Mode configurationOpen Command Prompt and run 'reg query HKLM\System\CurrentControlSet\Control\Session Manager /v SafeDllSearchMode' to check if Safe DLL Search Mode is enabled (value 1). Also verify via System Properties > Advanced > Environment Variables > Startup and Recovery > Environment.Affected if Safe DLL Search Mode is disabled (value 0), increasing the risk of DLL preloading.
You are affected if Autodesk Desktop Application version 7.0.16.29 or earlier is installed and the application directory contains untrusted DLL files or Safe DLL Search Mode is disabled.
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 dataImplement secure DLL loading by using full absolute paths for DLL imports, enabling safe DLL search mode, or using a DLL manifest to specify the load order. Users should be advised not to download or place untrusted DLL files in the application directory.
- Consultation6.0 h
- Implementation30.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7365 — 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-2019-7365 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