dbcve.org
Premiere ProApplication · Adobe

CVE-2020-9616

MEDIUM · 5.5 CVSS v3.1 Published 2020-06-26
Fix available
A fix is available. Upgrade to after 14.1 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
Adobe Premiere Pro versions 14.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 · moderate confidence

Adobe Premiere Pro versions 14.1 and earlier contain an out-of-bounds read vulnerability that allows attackers to read memory contents beyond allocated buffer boundaries, potentially exposing sensitive information such as credentials, session tokens, or other data residing in process memory.

MitigationUpdate Adobe Premiere Pro to a version newer than 14.1 to obtain the vendor patch addressing this vulnerability.

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
Premiere ProApplication
Affected:<= 14.1

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Verify Adobe Premiere Pro is installed
    Check for Premiere Pro installation by looking in typical install locations (Windows: C:\Program Files\Adobe\Adobe Premiere Pro 14\ or macOS: /Applications/Adobe Premiere Pro 14/) or search for premiere.exe (Windows) or Adobe Premiere Pro.app (macOS)
    Affected if Adobe Premiere Pro version 14.x or earlier is installed on the system
  2. Determine the installed version number
    Windows: Right-click premiere.exe, select Properties, go to Details tab to view File Version. macOS: Right-click Adobe Premiere Pro.app, select Get Info to view Version. Alternatively, open Premiere Pro and go to Help > About Adobe Premiere Pro to display the full version number
    Affected if The displayed version is 14.1 or any version below 14.1 (such as 14.0.x, 13.x, or earlier)
  3. Confirm the exact 14.x version if applicable
    If the version shows as 14.x, verify whether it is 14.1 or earlier by checking the full version string (for example, 14.0, 14.0.1, 14.0.2, 14.1)
    Affected if The version is 14.1, 14.0, 14.0.1, 14.0.2, or any 14.0.x release

A system is affected if Adobe Premiere Pro version 14.1 or any earlier version (14.0.x, 13.x, etc.) is installed, since the out-of-bounds read vulnerability exists in those versions.

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.

From vendor data
Upgrade available Upgrade to a release after 14.1
Interim mitigation

Update Adobe Premiere Pro to a version newer than 14.1 to obtain the vendor patch addressing this vulnerability.

Fix this in Premiere Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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