dbcve.org
Premiere ProApplication · Adobe

CVE-2023-47056

HIGH · 7.8 CVSS v3.1 Published 2023-11-16
Fix available
A fix is available. Upgrade to after 23.6 or later.
See remediation →
81/100
Remediation priority · High
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 version 24.0 (and earlier) and 23.6 (and earlier) are affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

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

A heap-based buffer overflow vulnerability in Adobe Premiere Pro versions 24.0 (and earlier) and 23.6 (and earlier) allows arbitrary code execution when a victim opens a malicious file. The vulnerability executes in the context of the current user and requires user interaction (opening a crafted file) for exploitation.

MitigationUpdate Adobe Premiere Pro to version 24.1 or later (or 23.6.1 or later for the 23.x branch). Until patched, avoid opening media files from untrusted or unknown sources.

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:<= 23.6= 24.0

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
High
Availability
High

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

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

  1. Check if Adobe Premiere Pro is installed
    On Windows, check Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Premiere Pro or look for the application in Program Files. On macOS, check /Applications/Adobe Premiere Pro or use 'ls /Applications | grep -i premiere'.
    Affected if Adobe Premiere Pro is not installed on the system.
  2. Determine installed Premiere Pro version
    On Windows, check the version in the application's properties (right-click Premiere Pro.exe > Properties > Details) or via Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Premiere Pro\Version. On macOS, right-click Adobe Premiere Pro.app > Get Info or run 'mdls -name kCFBundleShortVersionString /Applications/Adobe\ Premiere\ Pro.app'.
    Affected if The installed version cannot be determined or the application is not found.
  3. Compare version against affected range
    Match your installed version number against: 24.0 (all releases) and 23.6 or lower. The affected versions are: 23.6 and earlier, or exactly 24.0. Versions 23.6.1+ and 24.1+ are NOT affected.
    Affected if The installed version is 23.6, 23.5, 23.4, or any 23.x release <= 23.6, OR the installed version is exactly 24.0.

You are affected if Adobe Premiere Pro is installed AND the version is 24.0 or any release from 23.6 or earlier.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 23.6
Interim mitigation

Update Adobe Premiere Pro to version 24.1 or later (or 23.6.1 or later for the 23.x branch). Until patched, avoid opening media files from untrusted or unknown sources.

Recommended fix Moderate confidence

Premiere Pro 24.1 or later (or 23.6.1 if available for your subscription tier)

  1. Verify the installed Adobe Premiere Pro version by opening the application and navigating to Help > About Adobe Premiere Pro
  2. Close Adobe Premiere Pro completely
  3. Open Adobe Creative Cloud desktop application
  4. Navigate to the Apps tab or find Premiere Pro in your installed applications
  5. Click on Update to install the latest version, or manually download the update from helpx.adobe.com
Caveat Updating may require acceptance of new license terms; ensure project compatibility with new version before production use

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Premiere Pro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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