dbcve.org
3ds MaxApplication · Autodesk

CVE-2022-25793

HIGH · 7.8 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 2020.3.6 / 2021.3.10 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 Stack-based Buffer Overflow Vulnerability in Autodesk 3ds Max 2022, 2021, and 2020 may lead to code execution through the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer when parsing ActionScript Byte Code files. This vulnerability may allow arbitrary code execution on affected installations of Autodesk 3ds Max.

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

Stack-based buffer overflow in Autodesk 3ds Max 2020-2022 when parsing ActionScript Byte Code (ABC) files. The vulnerability stems from insufficient validation of user-supplied data length before copying into a fixed-size stack buffer, enabling potential arbitrary code execution.

MitigationApply vendor patches from Autodesk when available; avoid opening untrusted or unknown ABC files until patched; implement file type restrictions and sandboxing as compensating controls.

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:>= 2020, < 2020.3.6>= 2021, < 2021.3.10>= 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 go 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 falls within: 2020 (before 2020.3.6), 2021 (before 2021.3.10), or 2022 (through 2022.3.3)
  2. Verify exact product version number
    Run the application and check the splash screen on startup, or locate the 3dsmax.exe file and view its file properties to get the precise build number
    Affected if The exact version/build is lower than 2020.3.6, 2021.3.10, or 2022.3.3 respectively for your installed release year
  3. Determine if ABC file import functionality is present
    Check if the application can import or open ABC (ActionScript Byte Code) files through the File > Import menu or by testing with a sample ABC file
    Affected if ABC file import is available and the version is within the affected range listed above
  4. Review recent file access logs for ABC files
    Check application logs, Windows Event Viewer, or antivirus logs for any recent attempts to open or process .ABC files in 3ds Max
    Affected if ABC files have been opened in the affected software version

You are affected if Autodesk 3ds Max version 2020, 2021, or 2022 is installed and the specific build is below the patched versions (2020.3.6, 2021.3.10, or 2022.3.3), and ABC file parsing functionality exists in that installation.

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 2020.3.6 / 2021.3.10 or later
Fixed in 2020.3.62021.3.10
Interim mitigation

Apply vendor patches from Autodesk when available; avoid opening untrusted or unknown ABC files until patched; implement file type restrictions and sandboxing as compensating controls.

Recommended fix High confidence

3ds Max 2020.3.6 or later; 3ds Max 2021.3.10 or later; 3ds Max 2022.3.4 or later (latest 2022.x recommended)

  1. Verify current 3ds Max version by opening the application and navigating to Help > About Autodesk 3ds Max
  2. For 3ds Max 2020 users: Upgrade to version 2020.3.6 or later (2020.4.x recommended)
  3. For 3ds Max 2021 users: Upgrade to version 2021.3.10 or later (2021.4.x recommended)
  4. For 3ds Max 2022 users: Upgrade to version 2022.3.4 or later (2022.4.x or latest 2022.x release recommended)
  5. Download the updated version from the Autodesk Account portal at manage.autodesk.com
  6. Run the installer with administrator privileges and follow the on-screen prompts
  7. Restart the system after installation completes
  8. Verify the installed version matches the target fixed release
Caveat Standard upgrade risk: ensure project files are backed up before upgrading; verify plugin compatibility with new version

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

Fix this in 3ds Max Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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