CVE-2017-11303
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 · uneditedAn issue was discovered in Adobe Photoshop 18.1.1 (2017.1.1) and earlier versions. An exploitable memory corruption vulnerability exists. Successful exploitation could lead to arbitrary code execution.
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 confidenceMemory corruption vulnerability in Adobe Photoshop versions 18.1.1 and earlier that allows arbitrary code execution when processing specially crafted files.
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<= 18.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 Photoshop is installedOn Windows, check for Photoshop executable in common locations: C:\Program Files\Adobe\Adobe Photoshop CC 2017\Photoshop.exe or C:\Program Files\Adobe\Adobe Photoshop CC (year)\Photoshop.exe. On macOS, check /Applications/Adobe Photoshop CC 2017.app or similar.Affected if Adobe Photoshop is found on the system
-
Retrieve installed Photoshop version on WindowsRight-click the Photoshop.exe file, select Properties, then click the Details tab to view the Product Version field.Affected if Product version displays 18.1.1 or lower (e.g., 18.0, 17.x, 16.x, etc.)
-
Retrieve installed Photoshop version on macOSOpen Adobe Photoshop, go to Photoshop menu > About Photoshop to display the version number, or right-click the Adobe Photoshop app in Applications and select Get Info.Affected if Version displays 18.1.1 or lower (e.g., 18.0, 17.x, 16.x, etc.)
-
Identify vulnerable release familyPhotoshop versions 18.x correspond to Photoshop CC 2017. Versions 17.x correspond to Photoshop CC 2015.5. Any version within the 18.x family at 18.1.1 or below, or any 17.x or earlier release, is within the affected range.Affected if Version falls within the 18.1.1 or earlier range, or is any 17.x/16.x/earlier release
The system is affected if Adobe Photoshop is installed and the version number is 18.1.1 or any earlier version (18.0, 17.x, 16.x, etc.).
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.
From vendor dataUpdate Adobe Photoshop to the patched version provided by Adobe's security update.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11303 — 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-2017-11303 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