CVE-2020-3775
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 Photoshop CC 2019 versions 20.0.8 and earlier, and Photoshop 2020 versions 21.1 and earlier have a buffer errors vulnerability. 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 · moderate confidenceBuffer errors vulnerability in Adobe Photoshop CC 2019 (20.0.8 and earlier) and Photoshop 2020 (21.1 and earlier) allowing arbitrary code execution. Likely a memory corruption issue such as heap or stack buffer overflow when processing malformed image data.
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>= 21.0, <= 21.1>= 20.0, <= 20.0.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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.
-
Check installed Photoshop 2020 versionOpen Photoshop 2020, go to Help > About Photoshop, or check the version in the application properties. On Windows, you can also check in Programs and Features. On macOS, check in Applications folder Get Info.Affected if Version is between 21.0 and 21.1 inclusive
-
Check installed Photoshop CC 2019 versionOpen Photoshop CC 2019, go to Help > About Photoshop, or check the version in the application properties. On Windows, you can also check in Programs and Features. On macOS, check in Applications folder Get Info.Affected if Version is between 20.0 and 20.0.8 inclusive
-
Verify affected version rangesCompare your installed version number against the affected ranges: Photoshop 2020 versions 21.0 through 21.1, and Photoshop CC 2019 versions 20.0 through 20.0.8Affected if Your installed version falls within these ranges and no security patch has been applied
You are affected if you have Adobe Photoshop CC 2019 versions 20.0 to 20.0.8 or Photoshop 2020 versions 21.0 to 21.1 installed and have not applied the corresponding security update.
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 · scopedApply Adobe security updates to upgrade to patched Photoshop versions. Deploy via enterprise patch management or manual update to all affected installations.
Photoshop 2020 version 21.2.0+ or Photoshop CC 2019 version 20.0.9+
- Close Adobe Photoshop completely before updating
- Open Adobe Creative Cloud desktop application or navigate to helpx.adobe.com/photoshop
- Check your current Photoshop version via Help > About Photoshop in the application
- For Photoshop 2020 users: Upgrade to version 21.2.0 or later (the security update that addresses CVE-2020-3775)
- For Photoshop CC 2019 users: Upgrade to version 20.0.9 or later which contains the security patch
- Restart Photoshop after installation and verify the version number matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3775 — 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-2020-3775 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