CVE-2023-26343
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 Dimension versions 3.4.7 (and earlier) is 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 confidenceAdobe Dimension versions 3.4.7 and earlier contain an out-of-bounds read vulnerability. When a user opens a specially crafted malicious file, the application reads memory outside allocated bounds, potentially exposing sensitive memory contents and enabling ASLR bypass.
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< 3.4.8CVSS 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.
-
Check if Adobe Dimension is installedOn Windows, search for 'Adobe Dimension' in Add/Remove Programs or check the installation directory. On macOS, check /Applications for Adobe Dimension.app.Affected if Adobe Dimension is not installed on the system, the user is not affected by this vulnerability.
-
Determine the installed version of Adobe DimensionOpen Adobe Dimension, then go to Help > About Adobe Dimension to display the version number. Alternatively, check the application file properties in the installation folder.Affected if The exact version number cannot be determined, assume the product may be vulnerable.
-
Compare the installed version to the affected rangeCompare the version found in the previous step to the affected range: versions 3.4.7 and earlier are vulnerable. Version 3.4.8 and later are not vulnerable.Affected if The installed version is 3.4.7 or any earlier version (for example, 3.4.6, 3.4.5, etc.), the user is affected by this vulnerability.
-
Assess exposure to malicious filesDetermine if the user frequently opens .dgn, .3dm, or other 3D files from untrusted or unknown sources, as exploitation requires the user to open a specially crafted malicious file.Affected if Users routinely open files from untrusted sources, the likelihood of exploitation increases.
The user is affected if Adobe Dimension is installed and the installed version is 3.4.7 or earlier, and the user could potentially open a malicious crafted file.
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 · scoped3.4.8
Update Adobe Dimension to a version newer than 3.4.7. Users should avoid opening files from untrusted sources as exploitation requires user interaction.
Adobe Dimension 3.4.8
- Verify current Adobe Dimension version by opening the application and navigating to Help > About Adobe Dimension
- Close Adobe Dimension if it is currently open
- Open Adobe Creative Cloud desktop application or navigate to adobe.com/downloads
- Locate Adobe Dimension in your available applications
- Click the Update or Install button to install version 3.4.8
- Wait for the update to complete and verify the installation was successful
- Restart Adobe Dimension and confirm the version shows 3.4.8
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26343 — 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-26343 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