CVE-2019-7970
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 versions 19.1.8 and earlier and 20.0.5 and earlier have a type confusion 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 · high confidenceAdobe Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier contain a type confusion vulnerability that could allow an attacker to execute arbitrary code. The vulnerability stems from improper handling of object types in memory, potentially allowing an attacker to manipulate memory references and achieve 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<= 19.1.8>= 20.0, <= 20.0.5CVSS 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.
-
Locate Adobe Photoshop CC installationOpen Adobe Photoshop CC, go to Help > About Photoshop, or check the application file properties (right-click Photoshop.exe > Properties > Details) to find the exact version numberAffected if The installed version is 19.1.8 or earlier, or 20.0.5 or earlier
-
Confirm version numberNote the full version string displayed (for example, 19.1.8.12345 or 20.0.5.12345)Affected if Version starts with 19.1.8 or lower in the 19.x branch, or 20.0.5 or lower in the 20.x branch
-
Determine branch and compare to affected rangeFor 19.x branch: if version is 19.1.8 or earlier, it is affected. For 20.x branch: if version is 20.0.5 or earlier, it is affectedAffected if The version falls within <= 19.1.8 OR >= 20.0.0 and <= 20.0.5
You are affected if your installed Photoshop CC version is 19.1.8 or earlier in the 19.x branch, or 20.0.5 or earlier in the 20.x branch.
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 19.1.9 or later (for the 19.x branch) or version 20.0.6 or later (for the 20.x branch). Alternatively, apply the available security patches from Adobe.
Photoshop CC 2018 (19.1.9+) or Photoshop CC 2019 (20.0.6+)
- Identify your current Photoshop CC version via Help > About Photoshop
- If using version 19.x (Photoshop CC 2018), upgrade to version 19.1.9 or later
- If using version 20.x (Photoshop CC 2019), upgrade to version 20.0.6 or later
- Download the updated version from the official Adobe Creative Cloud desktop application or get.adobe.com/photoshop
- Close Photoshop completely before installing the update
- Run the Adobe Creative Cloud installer and allow the Photoshop update to complete
- Restart Photoshop and verify the version under Help > About Photoshop
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7970 — 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-2019-7970 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