dbcve.org
BridgeApplication · Adobe

CVE-2015-3111

HIGH · 10.0 CVSS v2.0 Published 2015-06-24
Fix available
A fix is available. Upgrade to after 15.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Heap-based buffer 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 confidence

Heap-based buffer overflow in Adobe Photoshop CC (versions before 16.0/2015.0.0) and Adobe Bridge CC (versions before 6.11) allows remote attackers to execute arbitrary code via unspecified vectors, potentially enabling complete system compromise.

MitigationUpdate Adobe Photoshop CC to version 16.0 or later and Adobe Bridge CC to version 6.11 or later. Prioritize patching given the critical CVSS 10 severity and active exploitation potential.

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
BridgeApplication
Affected:<= 6.1
Photoshop CcApplication
Affected:<= 15.2.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Adobe Photoshop CC is installed
    Check the Creative Cloud desktop app, or look for Adobe Photoshop CC in Program Files (Windows) or Applications (Mac). On Windows, also check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Photoshop for the Version key.
    Affected if Photoshop CC is installed and the version is 15.2.2 or earlier
  2. Determine Adobe Photoshop CC version
    Open Photoshop CC and go to Help > About Photoshop, or right-click the executable and select Properties > Details. On Windows, also query: reg query 'HKLM\SOFTWARE\Adobe\Photoshop' /v Version
    Affected if Version displays as 15.x.x or earlier (15.2.2 or below is vulnerable)
  3. Identify if Adobe Bridge CC is installed
    Check the Creative Cloud desktop app, or look for Adobe Bridge CC in Program Files (Windows) or Applications (Mac). On Windows, also check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Bridge CC for the Version key.
    Affected if Bridge CC is installed and the version is 6.1 or earlier
  4. Determine Adobe Bridge CC version
    Open Bridge CC and go to Help > About Adobe Bridge CC, or right-click the executable and select Properties > Details. On Windows, also query: reg query 'HKLM\SOFTWARE\Adobe\Bridge CC' /v Version
    Affected if Version displays as 6.1 or earlier (6.1 and below is vulnerable)

You are affected if either Adobe Photoshop CC version is 15.2.2 or earlier, or Adobe Bridge CC version is 6.1 or earlier.

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 15.2.2
Interim mitigation

Update Adobe Photoshop CC to version 16.0 or later and Adobe Bridge CC to version 6.11 or later. Prioritize patching given the critical CVSS 10 severity and active exploitation potential.

Recommended fix High confidence

Adobe Photoshop CC 16.0 (2015.0.0) or later / Adobe Bridge CC 6.11 or later

  1. 1. Open Adobe Creative Cloud desktop application or check for updates within the application
  2. 2. For Adobe Photoshop CC: Navigate to Updates and install Photoshop CC version 16.0 (2015.0.0) or later
  3. 3. For Adobe Bridge CC: Navigate to Updates and install Bridge CC version 6.11 or later
  4. 4. Alternatively, download the updates directly from helpx.adobe.com for your specific product
  5. 5. After installation, restart the applications to complete the update
  6. 6. Verify the installed version matches or exceeds the fixed release (Photoshop CC 16.0+, Bridge CC 6.11+)
Caveat Adobe CC subscriptions require active subscription; ensure compatibility with existing workflows and plugins before upgrading

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

Fix this in Bridge Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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