dbcve.org
Dwg TrueviewApplication · Autodesk

CVE-2022-42945

HIGH · 7.8 CVSS v3.1 Published 2022-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
DWG TrueViewTM 2023 version has a DLL Search Order Hijacking vulnerability. Successful exploitation by a malicious attacker could result in remote code execution on the target 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 · moderate confidence

DWG TrueView 2023 is vulnerable to DLL Search Order Hijacking, where the application loads Dynamic Link Libraries without fully qualifying the path. An attacker who can place a malicious DLL in a directory searched by the application (such as the application directory or a directory in the PATH) can achieve remote code execution when the application runs.

MitigationApply vendor patches from Autodesk when available. In the interim, ensure the DWG TrueView application directory is not writable by non-privileged users and verify that no untrusted directories exist in the system PATH before the legitimate DLL locations.

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
Dwg TrueviewApplication
Affected:= 2023

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
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 checks

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

  1. Confirm DWG TrueView 2023 is installed
    Open Windows Control Panel, go to Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*DWG TrueView*2023*"}' in PowerShell
    Affected if No entry found with DWG TrueView 2023 in the program name
  2. Verify the exact version number
    In Programs and Features, locate Autodesk DWG TrueView 2023 and note the version column, or check the executable properties at C:\Program Files\Autodesk\DWG TrueView 2023\DWGTrueView.exe
    Affected if Version shown is exactly 2023 (any minor update within the 2023 release line)
  3. Check if application directory is writable by low-privileged users
    Right-click the DWG TrueView 2023 installation folder (typically C:\Program Files\Autodesk\DWG TrueView 2023\), select Properties, go to Security tab, and verify that Users or Authenticated Users group does not have Write or Modify permissions
    Affected if Users or non-admin accounts have Write or Modify permissions on the application folder
  4. Inspect PATH environment variable for untrusted directories
    Open System Properties > Advanced > Environment Variables, review the System PATH variable, and list all directories that appear before C:\Program Files\Autodesk\DWG TrueView 2023\ or other trusted Autodesk paths
    Affected if User-writable directories (such as temp folders, downloads, or network shares) exist in PATH before legitimate program directories
  5. Identify DLLs loaded without full path
    Use Process Monitor from Sysinternals: run as administrator, filter by Process Name = DWGTrueView.exe, enable Registry and File activity, then start DWG TrueView 2023 and examine Result column for DLLs showing "NAME NOT FOUND" or paths like ".\dllname" without full qualification
    Affected if The application attempts to load DLLs from relative paths or directories outside its install folder without fully qualified paths

A user is affected if DWG TrueView 2023 is installed AND the application directory is writable by standard users OR untrusted directories precede trusted paths in the system PATH, allowing an attacker to place a malicious DLL for hijacking.

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

Apply vendor patches from Autodesk when available. In the interim, ensure the DWG TrueView application directory is not writable by non-privileged users and verify that no untrusted directories exist in the system PATH before the legitimate DLL locations.

Fix this in Dwg Trueview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42945 — 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-2022-42945 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