dbcve.org
Design ReviewApplication · Autodesk

CVE-2022-27866

HIGH · 7.8 CVSS v3.1 Published 2022-07-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 TIFF file when consumed through DesignReview.exe application can be forced to read beyond allocated boundaries when parsing the TIFF file. This vulnerability in conjunction with other vulnerabilities could lead to code execution 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 · high confidence

Out-of-bounds read vulnerability in Autodesk DesignReview.exe when parsing maliciously crafted TIFF files. The application reads beyond allocated memory boundaries during TIFF file processing, which could potentially be chained with other vulnerabilities to achieve code execution in the current process context.

MitigationApply vendor patch when available; avoid opening untrusted TIFF files in DesignReview.exe; consider application whitelisting or sandboxing as compensating controls until patch is applied.

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
Design ReviewApplication
Affected:= 2011= 2012= 2013= 2017= 2018

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. Locate DesignReview.exe installation
    Search for DesignReview.exe in typical installation directories: C:\Program Files\Autodesk\DesignReview\ or C:\Program Files (x86)\Autodesk\DesignReview\. You can also use PowerShell: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Recurse -Filter 'DesignReview.exe' -ErrorAction SilentlyContinue
    Affected if DesignReview.exe is found on the system
  2. Determine installed version of DesignReview.exe
    Right-click on DesignReview.exe, select Properties, then view the Details tab for Product Version. Alternatively, run: (Get-Item 'C:\Program Files\Autodesk\DesignReview\DesignReview.exe').VersionInfo.ProductVersion or use wmic product where "name like '%DesignReview%'" get version
    Affected if The installed version matches one of these: 2011, 2012, 2013, 2017, or 2018
  3. Verify application is configured to handle TIFF files
    Check file association for .tif and .tiff files: Open Default Programs or use assoc .tif command in Command Prompt to see if DesignReview.exe is associated with these file types. Also check if the TIFF parsing module is present in the installation directory
    Affected if DesignReview.exe is set as the default handler for .tif/.tiff files or users commonly open TIFF files with this application
  4. Confirm exposure to untrusted TIFF files
    Audit recent file access events for DesignReview.exe opening TIFF files. Check browser download folders, email attachments, or network shares where users may have opened TIFF files. Use Windows Event Logs: Security (event 4688) or Sysmon logs if available, filtering for DesignReview.exe and .tif/.tiff extensions
    Affected if Users have recently opened or are likely to open untrusted TIFF files using DesignReview.exe

The system is affected if Autodesk Design Review version 2011, 2012, 2013, 2017, or 2018 is installed AND the application is used to open TIFF files, particularly from untrusted sources.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available; avoid opening untrusted TIFF files in DesignReview.exe; consider application whitelisting or sandboxing as compensating controls until patch is applied.

Fix this in Design Review Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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