dbcve.org
Substance 3d ModelerApplication · Adobe

CVE-2024-53005

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to after 1.14.1 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Substance3D - Modeler versions 1.14.1 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 · high confidence

Out-of-bounds read vulnerability in Adobe Substance3D Modeler versions 1.14.1 and earlier allows reading sensitive memory contents beyond allocated buffers when a user opens a malicious file. The memory disclosure can leak addresses and other useful information, enabling attackers to bypass ASLR mitigation and potentially chain with other exploits.

MitigationUpdate Adobe Substance3D Modeler to the latest version when a patch becomes available. Avoid opening files from untrusted sources.

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
Substance 3d ModelerApplication
Affected:<= 1.14.1

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Verify Adobe Substance3D Modeler is installed
    Search your system for the application. On Windows, check Program Files, Program Files (x86), or the Adobe Creative Cloud folder. On macOS, check the Applications folder for 'Substance 3D Modeler'. Use your system search or installed programs list.
    Affected if The application is present on the system
  2. Determine the installed version number
    Open the application and go to Help > About Adobe Substance3D Modeler. Alternatively, on Windows, right-click the executable in File Explorer, select Properties, and view the Details tab. On macOS, right-click the app in Applications and select Get Info.
    Affected if Version is 1.14.1 or earlier, or the version cannot be verified
  3. Compare against affected versions
    The affected version range is all releases up to and including 1.14.1. If your version shows 1.14.1, 1.14.0, 1.13.x, or any earlier release, your installation falls within the vulnerable range.
    Affected if Installed version is 1.14.1 or earlier
  4. Identify the trigger condition
    This vulnerability requires a user to open a malicious file. Review which file types the application opens (typically .sbm, .fbx, .obj, .blend, or other 3D model formats) and consider whether you receive files from untrusted sources.
    Affected if You open files from untrusted or unknown sources in this application

Your environment is affected if Adobe Substance3D Modeler version 1.14.1 or earlier is installed and you open files in the application.

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 a release after 1.14.1
Interim mitigation

Update Adobe Substance3D Modeler to the latest version when a patch becomes available. Avoid opening files from untrusted sources.

Recommended fix Moderate confidence

Upgrade to the latest available version of Substance 3D Modeler (version > 1.14.1)

  1. Open Substance 3D Modeler
  2. Navigate to the application menu and select 'Help' > 'About Substance 3D Modeler' to check the current version
  3. If the version is 1.14.1 or earlier, close the application
  4. Open Adobe Creative Cloud desktop application
  5. Navigate to the 'Apps' section
  6. Find Substance 3D Modeler in the installed applications list
  7. Click on 'Update' or 'Install' to get the latest available version
  8. Wait for the update to download and install
Caveat Review Adobe's release notes for any new features or changes that may affect workflows

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

Fix this in Substance 3d Modeler Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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