CVE-2024-7992
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 DWG file, when parsed through Autodesk AutoCAD and certain AutoCAD-based products, can force a Stack-based Buffer Overflow. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code 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 confidenceA stack-based buffer overflow vulnerability exists in Autodesk AutoCAD and AutoCAD-based products when parsing maliciously crafted DWG files. The vulnerability allows an attacker to cause a crash, read sensitive data from stack memory, or achieve arbitrary code execution within the context of the running process.
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>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1CVSS 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 productOpen AutoCAD and go to Help > About Autodesk AutoCAD, or right-click the AutoCAD executable in the installation folder and select Properties > Details to view the Product version. Alternatively, check Add/Remove Programs for the installed AutoCAD variant.Affected if Any AutoCAD 2025 or AutoCAD-based product (Advance Steel, Architecture, Civil 3D, Electrical, LT, Mechanical, MEP) is listed as installed.
-
Confirm the exact version numberNote the full version string shown in the About dialog or file properties. For AutoCAD 2025, the version should display as a four-part number such as 2025.x.x.x.Affected if The version is shown in the format 2025.x.x.x.
-
Compare version against affected rangeVerify if the installed version falls within >= 2025.0.0 and < 2025.1.1. For example, versions like 2025.0.1, 2025.0.2, 2025.1.0 would be affected, while 2025.1.1 and later are patched.Affected if The installed version is 2025.0.0 through 2025.0.x or 2025.1.0, but lower than 2025.1.1.
-
Verify DWG file handling is possibleConfirm the installation includes DWG file handling capabilities by checking if the acad.exe or product-specific executable exists and can open .dwg files. The vulnerability triggers when parsing malicious DWG files.Affected if The product can open or process DWG files and the version is in the affected range.
You are affected if an AutoCAD 2025 or AutoCAD-based product (2025.0.x through 2025.1.0) is installed and can process 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 · scoped2025.1.1
Apply the vendor-supplied patch or update to AutoCAD and affected AutoCAD-based products as soon as possible. Implement file validation and restrict opening of DWG files from untrusted sources until patches are applied.
2025.1.1
- Verify current AutoCAD version by opening the application and navigating to Help > About AutoCAD
- Ensure all active work is saved and closed
- For network installations, contact your IT administrator to coordinate the update
- Download AutoCAD 2025.1.1 or later from the official Autodesk website (www.autodesk.com) or your Autodesk Account
- Run the installer with administrator privileges
- Follow the on-screen installation prompts to complete the upgrade
- Restart the workstation after installation completes
- Verify the installed version by checking Help > About AutoCAD to confirm version 2025.1.1 or later is now running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7992 — 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-2024-7992 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