CVE-2022-25788
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 · uneditedA maliciously crafted JT file in Autodesk AutoCAD 2022 may be used to write beyond the allocated buffer while parsing JT files. This vulnerability can be exploited to execute arbitrary code.
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 buffer overflow vulnerability exists in Autodesk AutoCAD 2022's JT file parser. When parsing a maliciously crafted JT file, the software writes data beyond the allocated buffer boundary, which can be leveraged to execute arbitrary code.
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>= 2022, < 2022.1.2>= 2022, < 2022.1.2>= 2022, < 2022.2.2>= 2022, < 2022.1.2>= 2022, < 2022.1.2>= 2022, < 2022.1.2>= 2022, < 2022.2.2>= 2022, < 2022.1.2>= 2022, < 2022.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
- 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.
-
Identify installed AutoCAD 2022 productOpen AutoCAD and go to Help > About AutoCAD, or check Add/Remove Programs for Autodesk AutoCAD 2022, Advance Steel 2022, AutoCAD Architecture 2022, Electrical 2022, LT 2022, Map 3D 2022, Mechanical 2022, or MEP 2022Affected if Any of these products are installed with a version below 2022.1.2 or between 2022.1.2 and 2022.2.2 (for AutoCAD, LT, and products with dual ranges)
-
Check installed version numberRun the command "ver" at the AutoCAD command line, or view the version in Help > About AutoCAD. Compare against the affected ranges: < 2022.1.2 OR >= 2022.1.2 and < 2022.2.2Affected if The version falls within any of the affected ranges for the installed product
-
Verify JT file handling is enabledCheck if the JT file parser is active by attempting to open a .jt file in AutoCAD, or check for registered JT file associations in Windows file type associationsAffected if JT files can be opened or parsed within the AutoCAD environment, enabling the vulnerable code path
If AutoCAD 2022 or its variants are installed with a version less than 2022.1.2 (or between 2022.1.2 and 2022.2.2 for AutoCAD/LT) and JT file parsing is enabled, the environment is affected by this vulnerability.
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 · scoped2022.1.22022.2.2
Apply the vendor-supplied patch for AutoCAD 2022 when released. Until then, restrict handling of JT files to trusted sources and disable automatic file parsing where possible.
AutoCAD/AutoCAD LT: 2022.2.2 or later; Other products: 2022.1.2 or later
- Identify the specific Autodesk product (e.g., AutoCAD, AutoCAD LT, Advance Steel, etc.) from the affected list
- Determine the current installed version by opening the application and navigating to Help > About Autodesk [Product]
- For AutoCAD and AutoCAD LT: Upgrade to version 2022.2.2 or later
- For all other affected products (Advance Steel, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP): Upgrade to version 2022.1.2 or later
- Verify the upgrade was successful by checking Help > About Autodesk [Product] shows the new version number
- Apply any available hotfixes or service packs from Autodesk's support website after upgrading
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25788 — 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-25788 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