CVE-2024-53006
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 · uneditedSubstance3D - Modeler versions 1.14.1 and earlier are affected by a NULL Pointer Dereference vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 confidenceSubstance3D Modeler versions 1.14.1 and earlier contain a NULL Pointer Dereference vulnerability that can be triggered when a user opens a maliciously crafted file. This causes the application to dereference a NULL pointer, resulting in a crash and denial-of-service condition.
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<= 1.14.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Locate Adobe Substance 3D Modeler installationOn Windows, check C:\Program Files\Adobe\Adobe Substance 3D Modeler\ or search for the application in Start menu. On macOS, check /Applications/ folder for 'Adobe Substance 3D Modeler.app'.Affected if The application is installed on the system
-
Determine installed version numberRight-click the executable or application file and select Properties (Windows) or Get Info (macOS). Look for the 'Version' or 'File version' field in the Details tab.Affected if A version number is displayed in the file properties
-
Compare against affected version rangeCompare the obtained version number to the affected range: 1.14.1 and earlier. If the version is 1.14.1 or any version lower than 1.14.1 (for example, 1.14.0, 1.13.x, etc.), the installed version falls within the vulnerable range.Affected if The installed version is 1.14.1 or lower
The environment is affected if Adobe Substance 3D Modeler version 1.14.1 or earlier is installed on the system.
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 · scopedUpdate Substance3D Modeler to a version newer than 1.14.1 when the patch becomes available. Additionally, train users to avoid opening files from untrusted sources.
Latest available version of Substance 3D Modeler (newer than 1.14.1) from Adobe official sources
- 1. Open Adobe Creative Cloud desktop application or navigate to the Adobe Substance 3D Modeler product page
- 2. Check for available updates to Substance 3D Modeler
- 3. If an update is available, download and install the latest version
- 4. Alternatively, visit helpx.adobe.com and search for Substance 3D Modeler updates or release notes
- 5. Verify the installed version is newer than 1.14.1 after update completion
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53006 — 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-2024-53006 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