dbcve.org
Advance SteelApplication · Autodesk

CVE-2024-7305

HIGH · 7.8 CVSS v3.1 Published 2024-08-20
Fix available
A fix is available. Upgrade to 2022.1.6 / 2023.1.7 or later.
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
A maliciously crafted DWF file, when parsed in AdDwfPdk.dll through Autodesk AutoCAD, may force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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 · moderate confidence

An out-of-bounds write vulnerability exists in AdDwfPdk.dll when parsing DWF files in Autodesk AutoCAD. A maliciously crafted DWF file can trigger the vulnerability, potentially allowing an attacker to cause a crash, corrupt data, or execute arbitrary code within the current process context.

MitigationAvoid opening untrusted or unverified DWF files in AutoCAD. Monitor for and apply Autodesk security updates once available to remediate this vulnerability.

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
Advance SteelApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1
AutocadApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1
Autocad LtApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1
Autocad MepApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.6>= 2025, < 2025.1

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. Identify installed Autodesk product
    Open the application and go to Help > About Autodesk AutoCAD, or check Add/Remove Programs for Autodesk AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, or Advance Steel
    Affected if Any of these products are installed
  2. Check product version
    In the affected application, type 'VER' or 'ABOUT' at the command prompt, or right-click the application in Add/Remove Programs and select Properties to view the version number
    Affected if The version is 2022.x, 2023.x, 2024.x, or 2025.x but falls below 2022.1.6, 2023.1.7, 2024.1.6, or 2025.1 respectively
  3. Locate vulnerable DLL
    Search for AdDwfPdk.dll in the application installation directory, typically found in C:\Program Files\Autodesk\[ProductName]\[Version]\ or C:\Program Files (x86)\Autodesk\[ProductName]\[Version]\
    Affected if The DLL exists in the installation folder, indicating the DWF parsing component is present
  4. Verify DWF file handling is enabled
    Open AutoCAD and attempt to open or import a DWF file, or check File > Open and confirm DWF appears as a supported format in the file type dropdown
    Affected if DWF files can be opened or imported in the application

You are affected if you have any listed AutoCAD product (2022 through 2025) at a version below the fixed releases AND you can open or import DWF files in that application.

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.

dbcve · scoped
Upgrade available Upgrade to 2022.1.6 / 2023.1.7 / 2024.1.6 or later
Fixed in 2022.1.62023.1.72024.1.6
Interim mitigation

Avoid opening untrusted or unverified DWF files in AutoCAD. Monitor for and apply Autodesk security updates once available to remediate this vulnerability.

Recommended fix High confidence

Upgrade to version 2022.1.6 or later for 2022 products; 2023.1.7 or later for 2023 products; 2024.1.6 or later for 2024 products; 2025.1 or later for 2025 products

  1. 1. Identify the currently installed Autodesk product version (e.g., AutoCAD 2023, AutoCAD LT 2024)
  2. 2. Determine which year-version you are running and note whether it falls within the vulnerable version ranges: 2022 (before 2022.1.6), 2023 (before 2023.1.7), 2024 (before 2024.1.6), 2025 (before 2025.1)
  3. 3. For AutoCAD products, launch the application and use the VER or ABOUT command to check the exact version number
  4. 4. Access Autodesk Account or the Autodesk Desktop App to download the latest update for your product year
  5. 5. Download the appropriate fixed version: 2022.1.6 or later, 2023.1.7 or later, 2024.1.6 or later, or 2025.1 or later
  6. 6. Install the update following Autodesk's standard installation procedures
  7. 7. Restart the application after installation
  8. 8. Verify the installed version matches or exceeds the minimum fixed version for your product year
Caveat Minor: Autodesk updates typically include bug fixes and stability improvements with minimal breaking changes; ensure compatibility with any custom scripts or plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Advance Steel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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