CVE-2021-27034
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 PICT, PCX, RCL or TIFF files in Autodesk Design Review 2018, 2017, 2013, 2012, 2011. 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 · high confidenceA heap-based buffer overflow vulnerability exists in Autodesk Design Review when parsing specially crafted PICT, PCX, RCL, or TIFF image files. The vulnerability occurs due to improper bounds checking during file parsing operations, allowing an attacker to overwrite heap memory and potentially execute arbitrary code via a malicious file.
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= 2011= 2012= 2013= 2017= 2018CVSS 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.
-
Confirm Autodesk Design Review installationLook for Autodesk Design Review in the list of installed programs via Windows Control Panel > Programs and Features, or search for the application executable (DesignReview.exe) in typical installation directories such as C:\Program Files\Autodesk\ or C:\Program Files (x86)\Autodesk\Affected if The application is installed on the system
-
Identify the installed version numberOpen Autodesk Design Review and navigate to Help > About Autodesk Design Review to view the exact version, or right-click DesignReview.exe in the installation folder, select Properties, and check the Details tab for the File VersionAffected if The displayed version matches 2011, 2012, 2013, 2017, or 2018
-
Verify the application can process vulnerable image formatsCheck if the software has the capability to open or preview image files. Attempt to verify whether PICT, PCX, RCL, or TIFF file handlers are registered with the application by examining file associations or attempting to open a sample of these file types in the softwareAffected if The application can parse PICT, PCX, RCL, or TIFF files and the installed version is one of the affected releases
You are affected if Autodesk Design Review version 2011, 2012, 2013, 2017, or 2018 is installed and the software can open or process PICT, PCX, RCL, or TIFF 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.
From vendor dataUsers should avoid opening untrusted or unsolicited PICT, PCX, RCL, or TIFF files in affected versions of Autodesk Design Review until an official patch is released by Autodesk. Upgrading to the latest patched version of the software is the primary remediation.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27034 — 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-27034 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