CVE-2023-27907
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 victim to open a malicious USD file that may trigger an out-of-bounds write vulnerability which may 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 confidenceThis is an out-of-bounds write vulnerability in Pixar's Universal Scene Description (USD) file parsing library. A specially crafted malicious USD file can trigger memory corruption during parsing, allowing an attacker to achieve 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.23.0CVSS 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.
-
Confirm Autodesk Maya Usd is installedCheck the installed Maya USD plugin or library version. In Maya, this can typically be found via the plugin manager or by checking the USD-related plug-in version metadata.Affected if The Maya USD plugin is present on the system
-
Identify the installed Maya USD versionLocate and inspect the Maya USD plug-in version. This is usually listed in the Maya Plug-in Manager under 'USD' or 'MayaUSD', or can be queried through Maya's built-in version information.Affected if A version is displayed in the plugin information
-
Compare installed version against the vulnerable rangeTake the installed version number and compare it to the affected range. The vulnerability affects versions less than 0.23.0.Affected if The installed version is lower than 0.23.0 (for example, 0.22.0, 0.21.0, etc.)
-
Verify USD file processing capabilityConfirm that the Maya USD import, export, or file loading functionality is enabled and accessible. Check if the user can load or parse USD files within the Maya environment.Affected if USD file loading or parsing features are available and functional
A user is affected if Autodesk Maya Usd with a version lower than 0.23.0 is installed and the system can process USD files.
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.
dbcve · scoped0.23.0
Avoid opening USD files from untrusted or unknown sources. Apply vendor security patches for USD libraries when released. Consider sandboxing applications that process USD files.
Maya Usd 0.23.0 or later
- Upgrade Maya Usd to version 0.23.0 or later to address the out-of-bounds write vulnerability
- Avoid opening untrusted or malicious USD files from untrusted sources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27907 — 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-27907 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