CVE-2015-3110
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 · uneditedInteger overflow in Adobe Photoshop CC before 16.0 (aka 2015.0.0) and Adobe Bridge CC before 6.11 allows attackers to execute arbitrary code via unspecified vectors.
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 confidenceInteger overflow vulnerability in Adobe Photoshop CC (before 16.0/2015.0.0) and Adobe Bridge CC (before 6.11) allows remote attackers to execute arbitrary code via unspecified vectors. The overflow likely occurs when processing malformed image files or other input, leading to heap corruption and code execution.
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<= 15.2.2<= 6.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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Adobe Photoshop CC versionOpen Photoshop, go to Help > About Photoshop, or check via Adobe Creative Cloud desktop app or Windows Programs and Features / macOS Applications folderAffected if Version is 15.2.2 or any 15.x version prior to 16.0 (2015.0.0)
-
Check Adobe Bridge CC versionOpen Bridge, go to Help > About Adobe Bridge, or check via Adobe Creative Cloud desktop app or Windows Programs and Features / macOS Applications folderAffected if Version is 6.1 or lower
You are affected if you have Adobe Photoshop CC version 15.2.2 or lower, or Adobe Bridge version 6.1 or lower, and process untrusted image files.
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 · scopedUpgrade Adobe Photoshop CC to version 16.0 or later and Adobe Bridge CC to version 6.11 or later. Alternatively, restrict access to untrusted image files and disable file previews until patches are applied.
Photoshop CC 16.0 (2015.0.0) or later; Bridge CC 6.11 or later
- For Adobe Photoshop CC: Upgrade to version 16.0 (2015.0.0) or later
- For Adobe Bridge CC: Upgrade to version 6.11 or later
- Use Adobe Creative Cloud desktop application to check for and apply updates, or download the updated versions from Adobe's website
- After upgrading, verify the new versions are installed correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3110 — 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-2015-3110 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