CVE-2020-3777
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 an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
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 Photoshop CC contains an out-of-bounds read vulnerability where the software reads memory beyond intended buffer boundaries. This can allow an attacker to extract sensitive information from the application's memory space, potentially including user data, credentials, or other process memory contents.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Photoshop 2020 version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Photoshop\ApplicationVersion (or HKEY_CURRENT_USER\Software\Adobe\Photoshop\ApplicatonVersion). Look for the 'Version' value (e.g., 21.0.x).Affected if Version is 21.0.0 through 21.1.x inclusive (21.0, 21.0.1, 21.0.2, 21.1, etc.)
-
Check Photoshop 2020 version on macOSRight-click Adobe Photoshop 2020 in the Applications folder, select 'Get Info', and read the Version number under the Adobe Photoshop 2020 name.Affected if Version is 21.0.x through 21.1.x inclusive
-
Check Photoshop CC 2019 version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Photoshop\ApplicationVersion. Look for the 'Version' value.Affected if Version is 20.0.0 through 20.0.8 inclusive (20.0, 20.0.1, 20.0.2... 20.0.8)
-
Check Photoshop CC 2019 version on macOSRight-click Adobe Photoshop CC 2019 in the Applications folder, select 'Get Info', and read the Version number.Affected if Version is 20.0.0 through 20.0.8 inclusive
Your environment is affected if Adobe Photoshop 2020 version 21.0 through 21.1 or Photoshop CC 2019 version 20.0 through 20.0.8 is installed and you process image files with the application.
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 dataApply the vendor security update from Adobe to obtain the patched version of Photoshop CC 2019 or 2020. Prioritize updating systems that process sensitive data or are exposed to untrusted image files.
- 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-2020-3777 — 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-3777 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