dbcve.org
3ds MaxApplication · Autodesk

CVE-2023-25002

HIGH · 7.8 CVSS v3.1 Published 2023-06-27
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 SKP file in Autodesk products is used to trigger use-after-free vulnerability. Exploitation of this vulnerability may lead to code execution.

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 confidence

A use-after-free vulnerability exists in Autodesk products when parsing maliciously crafted SKP (SketchUp) files. The vulnerability allows an attacker to execute arbitrary code by triggering a use-after-free condition through a specially crafted file that corrupts memory references.

MitigationApply vendor security updates from Autodesk when available. Until then, avoid opening SKP files from untrusted sources and consider disabling file handlers for SKP extensions in high-risk environments.

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:= 2022= 2023
NavisworksApplication
Affected:= 2022= 2023
RevitApplication
Affected:= 2022= 2023
VredApplication
Affected:= 2023

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 Autodesk products
    Open the Windows Control Panel, navigate to Programs and Features, or use the command 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software. Look for Autodesk 3ds Max, Autodesk Navisworks, Autodesk Revit, or Autodesk Vred.
    Affected if Any of these four products are listed in installed programs
  2. Verify the exact version number
    In the Programs and Features list or PowerShell output, confirm the version matches 2022 or 2023 exactly. For example, entries like 'Autodesk 3ds Max 2022' or 'Autodesk Revit 2023'. Check product-specific About dialog if available from the Help menu.
    Affected if The version is 2022 or 2023 for 3ds Max, Navisworks, or Revit, or version 2023 for Vred
  3. Confirm SKP file handling capability
    Launch the installed Autodesk product and attempt to access the Open or Import dialog. Navigate to the file type dropdown and look for '.SKP' or 'SketchUp Files' as an available format. Alternatively, right-click a .SKP file in Windows Explorer and check if it shows the Autodesk product in the 'Open with' context menu.
    Affected if SKP file type appears as an importable or openable format in the product, indicating the vulnerable file parser is present
  4. Check for recent file access or SKP imports
    Review the application's recent files list or check the Windows %APPDATA% folder for the specific product's recent documents. On Windows, common paths include %APPDATA%\Autodesk\3dsMax\2022\ or similar version-specific folders under the product's folder.
    Affected if Recent SKP files appear in the application's recent files or any SKP import/open activity has occurred

A user is affected if they have Autodesk 3ds Max 2022/2023, Navisworks 2022/2023, Revit 2022/2023, or Vred 2023 installed with SKP file handling enabled and have opened or could open malicious SKP files.

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 security updates from Autodesk when available. Until then, avoid opening SKP files from untrusted sources and consider disabling file handlers for SKP extensions in high-risk environments.

Fix this in 3ds Max Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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