CVE-2023-25007
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 malicious actor may convince a user to open a malicious USD file that may trigger an uninitialized pointer which could result in 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 confidenceThe vulnerability is an uninitialized pointer flaw in software that parses USD (Universal Scene Description) files. When a user opens a specially crafted malicious USD file, the uninitialized pointer is dereferenced, potentially allowing an attacker to achieve arbitrary code execution on the victim's machine.
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<= 0.3CVSS 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.
-
Identify if Autodesk 3ds Max is installedCheck the Windows Program Files directory for 3ds Max installation (typically C:\Program Files\Autodesk\3ds Max) or look in Windows Registry under HKLM\SOFTWARE\Autodesk\3dsMaxAffected if 3ds Max is installed and the USD plugin component exists on the system
-
Determine the version of the Autodesk 3ds Max USD pluginLocate the USD plugin DLLs in the 3ds Max plugins or modules directory and check the file version properties, or run '3dsmax.exe -version' if available and check the installed plug-in versions listed in the 3ds Max UI under Plug-in ManagerAffected if The USD plugin version is 0.3 or lower (any version up to and including 0.3)
-
Check if the USD import/load functionality is enabledOpen 3ds Max and verify whether the USD import/export features are available in the File > Import menu or check the Plug-in Manager for loaded USD-related pluginsAffected if USD import/export capabilities are present and loaded in 3ds Max
-
Inspect recent USD file activityReview Windows Event Logs for 3ds Max process activity involving .usd, .usda, .usdc, or .usdz file extensions, or check the user's recent documents for USD files opened with 3ds MaxAffected if Users have recently opened or imported USD files from potentially untrusted sources
The environment is affected if Autodesk 3ds Max is installed with a USD plugin version 0.3 or lower and users process USD files with it.
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 dataOrganizations should implement controls preventing users from opening USD files from untrusted sources, and apply vendor patches for affected software when available. User awareness training about the risks of opening untrusted file attachments is also recommended.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25007 — 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-2023-25007 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