dbcve.org
3ds MaxApplication · Autodesk

CVE-2022-27531

HIGH · 7.8 CVSS v3.1 Published 2022-06-16
Fix available
A fix is available. Upgrade to 2021.3.8 / 2022.3.3 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 TIF file can be forced to read beyond allocated boundaries in Autodesk 3ds Max 2022, and 2021 when parsing the TIF files. 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 3ds Max 2021 and 2022 TIF file parser. A maliciously crafted TIF file can trigger reads beyond allocated memory boundaries. While this is an information disclosure issue, the CVSS notes it can facilitate code execution when chained with other vulnerabilities.

MitigationDo not open untrusted TIF files in affected 3ds Max versions. Update to the latest Autodesk 3ds Max version which includes the security patch for this vulnerability.

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
3ds MaxApplication
Affected:>= 2021, < 2021.3.8>= 2022, < 2022.3.3

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 3ds Max version
    Open 3ds Max and navigate to Help > About Autodesk 3ds Max, or right-click the 3dsmax.exe file in the installation directory and select Properties > Details to view the Product version.
    Affected if The version displayed is 2021.x (where x < 3.8) or 2022.x (where x < 3.3), indicating it falls within the vulnerable range.
  2. Confirm the TIF file parser component exists
    Verify the 3ds Max installation includes the file import functionality by attempting to access File > Import or checking for TIF-related plugins in the plugins or bin directory.
    Affected if The TIF import capability is present and usable within the application, meaning the vulnerable parser code is loaded.
  3. Compare version against vulnerability thresholds
    Document the exact version number (for example, 2021.1.5 or 2022.2.1) and compare it against the affected ranges: 2021 versions prior to 2021.3.8, and 2022 versions prior to 2022.3.3.
    Affected if The installed version is 2021.x where x is less than 3.8, or 2022.x where x is less than 3.3.

A user is affected if they have Autodesk 3ds Max 2021 version 2021.3.7 or earlier, or version 2022.3.2 or earlier, and they import or open TIF files using the built-in parser.

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 2021.3.8 / 2022.3.3 or later
Fixed in 2021.3.82022.3.3
Interim mitigation

Do not open untrusted TIF files in affected 3ds Max versions. Update to the latest Autodesk 3ds Max version which includes the security patch for this vulnerability.

Recommended fix High confidence

3ds Max 2021.3.8 for 2021.x users; 3ds Max 2022.3.3 for 2022.x users

  1. Close all running instances of Autodesk 3ds Max
  2. Navigate to the Autodesk Account portal or official Autodesk support site at www.autodesk.com
  3. Locate the downloads section for 3ds Max
  4. For 3ds Max 2021: Download and install version 2021.3.8 or later
  5. For 3ds Max 2022: Download and install version 2022.3.3 or later
  6. Restart 3ds Max and verify the application launches without errors

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

Fix this in 3ds Max 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-2022-27531 — 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-27531 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