dbcve.org
Advance SteelApplication · Autodesk

CVE-2021-27041

HIGH · 7.8 CVSS v3.1 Published 2021-06-25
Fix available
A fix is available. Upgrade to 2019.1.3 / 2020.1.4 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 DWG file can be used to write beyond the allocated buffer while parsing DWG 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 · moderate confidence

A buffer overflow vulnerability exists in the DWG file parsing functionality where a maliciously crafted DWG file causes a write operation beyond the allocated buffer boundary during parsing. This memory corruption can be leveraged to achieve arbitrary code execution.

MitigationRestrict processing of DWG files from untrusted or unknown sources, and apply vendor security patches (typically from Autodesk for AutoCAD-based products) as soon as they become available.

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.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, < 2022.0.1
AutocadApplication
Affected:>= 2019, < 2019.1.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, < 2022.0.1
Autocad ArchitectureApplication
Affected:>= 2019, < 2019.1.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, <= 2022.0.1
Autocad ElectricalApplication
Affected:>= 2019, < 2019.1.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, < 2022.0.1
Autocad LtApplication
Affected:>= 2019, < 2019.1.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, < 2022.0.1
Autocad Map 3dApplication
Affected:>= 2019, < 2019.1.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, < 2022.0.1
Autocad MechanicalApplication
Affected:>= 2019, < 2019.1.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, < 2022.0.1
Autocad MepApplication
Affected:>= 2019, < 2019.1.3>= 2020, < 2020.1.4>= 2021, < 2021.1.1>= 2022, < 2022.0.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
    Check the list of installed programs on the system for any of these: Autodesk Advance Steel, Autodesk AutoCAD, Autodesk AutoCAD Architecture, Autodesk AutoCAD Electrical, Autodesk AutoCAD LT, Autodesk AutoCAD Map 3D, Autodesk AutoCAD Mechanical, or Autodesk AutoCAD MEP. On Windows, this can be done via Control Panel > Programs and Features, or by querying the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
    Affected if Any of the listed products appears in the installed programs list
  2. Determine product version
    Open the installed Autodesk application, then go to Help > About (or use the About command). Alternatively, check the Windows registry under HKLM\SOFTWARE\Autodesk\<ProductName>\<Version>\InstallPath for the version key
    Affected if The version displayed is unclear or cannot be determined from the application
  3. Compare against vulnerable 2019 versions
    If the product version starts with 2019 (for example, 2019.0.x), check if it is earlier than 2019.1.3. Look at the full version string displayed in the About dialog or registry
    Affected if The installed version is 2019.x and is lower than 2019.1.3 (for example, 2019, 2019.0.1, 2019.1.0, 2019.1.1, 2019.1.2)
  4. Compare against vulnerable 2020-2022 versions
    If the product version starts with 2020, 2021, or 2022, compare: for 2020, check if below 2020.1.4; for 2021, check if below 2021.1.1; for 2022, check if below 2022.0.1
    Affected if The installed version is 2020.x and lower than 2020.1.4, OR 2021.x lower than 2021.1.1, OR 2022.x lower than 2022.0.1

The environment is affected if any of the listed Autodesk products is installed with a version that falls within the vulnerable ranges (2019 < 2019.1.3, 2020 < 2020.1.4, 2021 < 2021.1.1, or 2022 < 2022.0.1).

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.

From vendor data
Upgrade available Upgrade to 2019.1.3 / 2020.1.4 / 2021.1.1 or later
Fixed in 2019.1.32020.1.42021.1.1
Interim mitigation

Restrict processing of DWG files from untrusted or unknown sources, and apply vendor security patches (typically from Autodesk for AutoCAD-based products) as soon as they become available.

Fix this in Advance Steel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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