dbcve.org
Advance SteelApplication · Autodesk

CVE-2022-27529

HIGH · 7.8 CVSS v3.1 Published 2022-04-18
Fix available
A fix is available. Upgrade to 2019.1.4 / 2020.1.5 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 PICT, BMP, PSD or TIF file in Autodesk AutoCAD 2022, 2021, 2020, 2019 may be used to write beyond the allocated buffer while parsing PICT, BMP, PSD or TIF file. This vulnerability may 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 confidence

A buffer overflow vulnerability exists in AutoCAD 2022, 2021, 2020, and 2019 when parsing maliciously crafted PICT, BMP, PSD, or TIF image files. The software writes data beyond the allocated buffer boundary during file parsing, which can be leveraged to achieve arbitrary code execution.

MitigationApply the vendor patch from Autodesk to affected AutoCAD installations. Until patched, avoid opening untrusted or received PICT, BMP, PSD, or TIF files in vulnerable AutoCAD versions.

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:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
AutocadApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2022, < 2022.2.2
Autocad ArchitectureApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad ElectricalApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad LtApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2022, < 2022.2.2
Autocad Map 3dApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad MechanicalApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad MepApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2

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 AutoCAD or related product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, or Advance Steel). Go to Help > About Autodesk [Product Name] to see the exact product name and version displayed in the splash screen or about dialog.
    Affected if The product is any of the listed affected products: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, or Advance Steel.
  2. Locate version information in Windows
    Open Windows Control Panel > Programs and Features (or Settings > Apps). Find the Autodesk product in the list. Note the version column entry (e.g., 2022.0.1, 2021.1.0, etc.).
    Affected if A version is listed in the Programs and Features list that matches the affected version ranges.
  3. Check version from application
    Within the AutoCAD application, type 'VER' or 'ABOUT' at the command line and press Enter. The version and build number will display. Record the full version string.
    Affected if The version displayed is within the affected 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 / 2022.2.2 depending on product).
  4. Compare against vulnerable version ranges
    Review the recorded version number against these thresholds: 2019 versions below 2019.1.4 are vulnerable; 2020 versions below 2020.1.5 are vulnerable; 2021 versions below 2021.1.2 are vulnerable; 2022 versions below 2022.1.2 (or below 2022.2.2 for AutoCAD and AutoCAD LT) are vulnerable.
    Affected if Your installed version falls within any of these vulnerable ranges.

You are affected if you are running any of the listed Autodesk products (AutoCAD, AutoCAD Architecture, Electrical, LT, Map 3D, Mechanical, MEP, or Advance Steel) at version 2019.x before 1.4, 2020.x before 1.5, 2021.x before 1.2, or 2022.x before 1.2 (or 2.2 for standard AutoCAD/LT).

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 2019.1.4 / 2020.1.5 / 2021.1.2 or later
Fixed in 2019.1.42020.1.52021.1.2
Interim mitigation

Apply the vendor patch from Autodesk to affected AutoCAD installations. Until patched, avoid opening untrusted or received PICT, BMP, PSD, or TIF files in vulnerable AutoCAD versions.

Recommended fix High confidence

Upgrade to the minimum fixed version for your release year: 2019.1.4, 2020.1.5, 2021.1.2, or 2022.1.2 (or later)

  1. Identify your current AutoCAD product version by opening the application and going to Help > About AutoCAD
  2. Note the exact version number (e.g., 2022.0.1 or 2022.1.1)
  3. Determine which release year your version falls into (2019, 2020, 2021, or 2022)
  4. For AutoCAD 2022: Upgrade to version 2022.1.2 or later
  5. For AutoCAD 2021: Upgrade to version 2021.1.2 or later
  6. For AutoCAD 2020: Upgrade to version 2020.1.5 or later
  7. For AutoCAD 2019: Upgrade to version 2019.1.4 or later
  8. Download the update from Autodesk Account (accounts.autodesk.com) or use Help > Check for Updates within the application
Caveat Standard Autodesk update; no major breaking changes expected for minor version upgrades within same release year

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

Fix this in Advance Steel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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