CVE-2023-47080
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 · uneditedAdobe Substance 3D Stager versions 2.1.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 · moderate confidenceAdobe Substance 3D Stager versions 2.1.1 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. Attackers can exploit this by crafting a malicious file that, when opened by a victim, enables memory disclosure to potentially bypass ASLR security mitigations.
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<= 2.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Substance 3D Stager is installedCheck your system for the Adobe Substance 3D Stager application - on Windows, look in Add or Remove Programs or the installation directory; on Mac, check the Applications folder.Affected if The software is present on the system
-
Determine the installed versionOpen Adobe Substance 3D Stager and navigate to Help > About, or right-click the application in your programs list to view version information.Affected if The displayed version number is 2.1.1 or any earlier version (such as 2.1.0, 2.0.x, etc.)
-
Compare against affected version rangeCheck if the installed version falls within the affected range: any version numbered 2.1.1 or lower.Affected if The installed version is 2.1.1 or earlier, indicating the vulnerable version is in use
-
Assess user interaction riskDetermine whether the application is used to open files from external or untrusted sources, as exploitation requires a user to open a maliciously crafted file.Affected if Users routinely open files from untrusted sources using Adobe Substance 3D Stager, which would enable the exploitation vector
You are affected if Adobe Substance 3D Stager version 2.1.1 or earlier is installed and users may 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 · scopedUpdate Adobe Substance 3D Stager to the latest patched version. Additionally, educate users to avoid opening files from untrusted sources, as exploitation requires user interaction.
Adobe Substance 3D Stager 2.1.2
- Open Adobe Substance 3D Stager
- Navigate to the Help menu and select 'Check for Updates' or 'Sign In' to your Adobe account
- Follow the prompts to download and install the latest version (2.1.2 or later)
- Alternatively, visit the Adobe website directly and download the newest release from the official Adobe Substance 3D Stager download page
- Restart the application after the update completes
- Verify the installed version is 2.1.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47080 — 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-47080 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