CVE-2022-27867
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, 2021, 2020, 2019 can be used to trigger use-after-free vulnerability. Exploitation of this vulnerability may lead to code execution.
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 use-after-free vulnerability exists in the JT file parsing component of Autodesk AutoCAD 2022, 2021, 2020, and 2019. When processing a maliciously crafted JT file, the software fails to properly manage memory allocation and deallocation, allowing an attacker to potentially execute arbitrary code by exploiting the dangling pointer.
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= 2020= 2021= 2022CVSS 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.
-
Verify AutoCAD installation existsCheck for AutoCAD installation directory (typically in Program Files\Autodesk\) or look for AutoCAD entry in Windows registry under HKLM\SOFTWARE\Autodesk\AutoCADAffected if AutoCAD is installed on the system
-
Determine installed AutoCAD versionCheck the version folder name in the AutoCAD installation directory, or run 'reg query "HKLM\SOFTWARE\Autodesk\AutoCAD" /s' to enumerate installed versionsAffected if Version matches 2019, 2020, 2021, or 2022
-
Confirm JT file handler is presentVerify the JT file parsing component exists by checking for JTCore.dll or similar JT-handling modules in the AutoCAD installation folderAffected if JT file handling capability is present (standard in affected versions)
A user is affected if AutoCAD version 2019, 2020, 2021, or 2022 is installed and the software can open or process JT files, which is the typical default configuration for these versions.
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 · scopedUsers should avoid opening JT files from untrusted sources. Autodesk has released patches for affected versions; ensure AutoCAD installations are updated to the latest patched versions.
AutoCAD 2022.1.2 or later (or latest service pack for respective version)
- 1. Open Autodesk Account or Autodesk Desktop Connector
- 2. Navigate to Products and Services section
- 3. Locate Autodesk AutoCAD 2022, 2021, 2020, or 2019
- 4. Download and install the latest available update or service pack for your installed version
- 5. Alternatively, navigate to www.autodesk.com/support and search for CVE-2022-27867 to obtain the specific security update
- 6. Restart AutoCAD after installation
- 7. Verify the update was applied successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27867 — 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-27867 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