CVE-2024-49515
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 - Painter versions 10.1.0 and earlier are affected by an Untrusted Search Path vulnerability that might allow attackers to execute arbitrary code. If the application uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted application would then execute. The problem extends to any type of critical resource that the application trusts. 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 confidenceSubstance3D Painter versions 10.1.0 and earlier use an untrusted search path to locate critical resources and programs. An attacker can place a malicious executable in a location that precedes the legitimate resource in the search path, causing the application to execute the attacker's code when a victim opens a malicious file.
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< 10.1.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
- 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.
-
Verify Adobe Substance 3D Painter versionOpen the application and go to Help > About Adobe Substance 3D Painter, or check the installed version via the Adobe Creative Cloud desktop application or Windows Programs and FeaturesAffected if The installed version is 10.1.0 or earlier, meaning it is less than 10.1.1
-
Inspect the application installation directory for unexpected executablesBrowse to the Adobe Substance 3D Painter installation folder (typically in Program Files/Adobe or Program Files/Adobe/Adobe Substance 3D Painter) and look for any .exe files that were not installed by Adobe or that appear suspiciousAffected if Any untrusted or unknown executable files exist in the application directory that could be invoked before the legitimate application binaries
-
Check the working directory for untrusted executablesIdentify the typical working directories where you open or save Substance 3D Painter files, and examine these folders for any .exe files that should not be presentAffected if Any executable files exist in working directories where you open or save project files that could be invoked due to the search path vulnerability
-
Review file opening practicesConsider whether you or your team members commonly open .sbsar, .sbs, or project files from untrusted or unknown sources, particularly from downloads, email attachments, or external mediaAffected if Users open files from untrusted sources in the application, which could trigger the malicious executable placement scenario described in the CVE
Your environment is affected if Adobe Substance 3D Painter version is 10.1.0 or earlier and there are untrusted executables present in the application directory, working directories, or if users open files from untrusted sources.
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 · scoped10.1.1
Update to a version newer than 10.1.0 when a patch is available. Until then, ensure the application directory and working directory contain no untrusted executables and avoid opening files from untrusted sources.
10.1.1
- Download Substance 3D Painter version 10.1.1 or later from the official Adobe source (helpx.adobe.com)
- Install the updated version of Substance 3D Painter
- Restart the application if it was running during the update
- Verify the installed version is 10.1.1 or later by checking About/Version information in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49515 — 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-49515 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