CVE-2023-47055
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 Premiere Pro version 24.0 (and earlier) and 23.6 (and earlier) are affected by a Use After Free 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 · high confidenceA Use After Free vulnerability in Adobe Premiere Pro versions 24.0 and earlier, and 23.6 and earlier, allows arbitrary code execution when a user opens a malicious file. The vulnerability stems from improper memory management where memory is freed but subsequently accessed, potentially leading to code execution in the context of the current user.
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<= 23.6= 24.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Adobe Premiere Pro is installedLook for Adobe Premiere Pro in your installed applications - on Windows check Programs and Features or the installation directory (typically C:\Program Files\Adobe\Adobe Premiere Pro), on macOS check the Applications folder.Affected if Adobe Premiere Pro is present on the system
-
Identify the installed Premiere Pro versionOpen Premiere Pro and go to Help > About Adobe Premiere Pro to view the exact version number, or locate the application in your system and check its properties for version information.Affected if The displayed version falls within the affected ranges: any version <= 23.6 or version 24.0 exactly
-
Verify the vulnerable condition is reachableConfirm that the application can open project files (.prproj) or other media files, as exploitation requires the user to open a malicious file.Affected if Users can open project or media files from untrusted sources within Premiere Pro
-
Confirm user access levelCheck the Windows user account context (User or Administrator) or macOS user privileges under which Premiere Pro runs.Affected if The application runs with elevated privileges, as exploitation executes code in the context of the current user
You are affected if Adobe Premiere Pro is installed and the installed version is either 24.0 or any version 23.6 or earlier.
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 · scopedUpdate Adobe Premiere Pro to the latest patched version. Additionally, enforce user awareness to avoid opening untrusted or unsolicited files, as exploitation requires user interaction.
Premiere Pro 24.1 or later (24.x latest stable release)
- Open Adobe Creative Cloud desktop application or navigate to the Adobe website
- Locate Adobe Premiere Pro in your installed applications
- Check for available updates - Adobe will typically push security updates automatically or via manual check
- Alternatively, visit helpx.adobe.com and search for Premiere Pro security updates
- Download and install the latest version of Premiere Pro (version 24.1 or later)
- Restart your computer after installation to ensure all components are updated
- Verify the installed version by opening Premiere Pro and checking Help > About Adobe Premiere Pro
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47055 — 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-2023-47055 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