CVE-2022-27524
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 · uneditedAn out-of-bounds read can be exploited in Autodesk TrueView 2022 may lead to an exposure of sensitive information or a crash through using a maliciously crafted DWG file as an Input. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.
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 confidenceAn out-of-bounds read vulnerability in Autodesk TrueView 2022 allows attackers to exploit maliciously crafted DWG files as input, potentially exposing sensitive information from memory or causing a crash. When chained with other vulnerabilities, this could lead to code execution in the current process context.
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>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 TrueView installationCheck Program Files for 'Autodesk\Dwg TrueView' folder, or look for the application in Windows Programs and FeaturesAffected if TrueView is installed on the system
-
Identify installed TrueView versionOpen Windows Programs and Features, find Autodesk Dwg TrueView, and note the version number in the 'Version' column; alternatively, right-click the executable and view Properties > Details for version infoAffected if Version matches any of these ranges: 2019.x before 2019.1.4, 2020.x before 2020.1.5, 2021.x before 2021.1.2, or 2022.x before 2022.1.2
-
Confirm vulnerable component is presentVerify the TrueView installation includes the DWG file handling component (typically in the installation directory as core DLLs like 'acdb18.dll' or similar)Affected if The DWG processing components exist and the application can open DWG files
-
Assess exposure to untrusted DWG filesReview whether users in your environment open DWG files from external or untrusted sources using TrueViewAffected if Users regularly open DWG files from untrusted or unknown sources in TrueView
If Autodesk Dwg TrueView is installed with a version that falls within any of the affected ranges (2019 to <2019.1.4, 2020 to <2020.1.5, 2021 to <2021.1.2, or 2022 to <2022.1.2), the system is vulnerable when processing malicious DWG files.
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 · scoped2019.1.42020.1.52021.1.2
Avoid opening untrusted or unverified DWG files in TrueView 2022 until an official patch is available; consider applying available security updates from Autodesk and implementing file sandboxing for untrusted DWG inputs.
DWG TrueView 2022.1.2 or later (or the latest available version per your release cycle)
- 1. Close Autodesk DWG TrueView if it is currently running
- 2. Navigate to the Autodesk website or use the Autodesk Desktop App to check for available updates
- 3. Download the latest version of DWG TrueView (2022.1.2 or later)
- 4. Run the installer and follow the on-screen prompts to complete the installation
- 5. After installation, verify the version by opening DWG TrueView and checking Help > About Autodesk DWG TrueView
- 6. Ensure the installed version is 2019.1.4 or higher, 2020.1.5 or higher, 2021.1.2 or higher, or 2022.1.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27524 — 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-2022-27524 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