CVE-2021-40164
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 heap-based buffer overflow could occur while parsing TIFF, PICT, TGA, or RLC files. 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 · moderate confidenceHeap-based buffer overflow in image file parsing for TIFF, PICT, TGA, and RLC formats. The vulnerability allows heap memory corruption during file parsing, potentially enabling arbitrary code execution with user-level privileges.
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, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2020, < 2020.3.2>= 2021, < 2021.1.2>= 2021, < 2021.2.2>= 2022, < 2022.1.2>= 2022, < 2022.2.2>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2CVSS 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 Autodesk productOpen AutoCAD and go to Help > About Autodesk AutoCAD, or check Programs and Features in Control Panel for the installed product name (e.g., AutoCAD 2021, AutoCAD Architecture 2021, AutoCAD Civil 3D 2022)Affected if The product is one of: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, or AutoCAD Mechanical
-
Determine installed version numberIn AutoCAD, type 'VER' or 'ABOUT' at the command line, or look at the version in Help > About. Note the full version including the update/release number (e.g., 2021.1)Affected if Version starts with 2019, 2020, 2021, or 2022 but does not match the patched versions below
-
Compare against affected version rangesCheck if your version falls into any of these ranges: 2019.x before 2019.1.4; 2020.x before 2020.1.5 (LT also before 2020.3.2); 2021.x before 2021.1.2 (LT also before 2021.2.2); 2022.x before 2022.1.2 (LT also before 2022.2.2)Affected if Your installed version is within any of these vulnerable ranges
-
Determine if image parsing is usedThe flaw triggers when opening or importing TIFF, PICT, TGA, or RLC image files. Check if users in your environment work with these image formats in the affected AutoCAD productAffected if Users routinely open or attach files in these formats using the affected product version
You are affected if you have any of the listed AutoCAD products installed at a version within the vulnerable ranges and users parse TIFF, PICT, TGA, or RLC image 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 · scoped2019.1.42020.1.52020.3.2
Apply vendor-supplied patches to the affected software. Until patched, exercise caution when opening untrusted image files in the affected formats.
Upgrade to the first fixed version in your product line: 2019.1.4, 2020.1.5, 2020.3.2 (LT only), 2021.1.2, or 2022.1.2
- Identify the exact version of the installed Autodesk product (Help > About AutoCAD > Product Information)
- Determine the product line (AutoCAD, AutoCAD LT, AutoCAD Civil 3D, etc.)
- For AutoCAD 2019: Upgrade to version 2019.1.4 or later
- For AutoCAD 2020: Upgrade to version 2020.1.5 or later
- For AutoCAD 2021: Upgrade to version 2021.1.2 or later
- For AutoCAD 2022: Upgrade to version 2022.1.2 or later
- For AutoCAD LT 2020: Also accept version 2020.3.2 or later as a valid fix
- Download the appropriate update from the Autodesk Account portal or Autodesk Desktop App
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40164 — 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-2021-40164 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