CVE-2023-47058
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 an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 confidenceAdobe Premiere Pro versions 24.0 and earlier, and 23.6 and earlier contain an out-of-bounds read vulnerability when parsing crafted files. The vulnerability allows reading past the end of an allocated memory structure, which an attacker could leverage to execute arbitrary code in the context of the current user. Exploitation requires user interaction—specifically, opening a malicious file.
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.
-
Identify installed Adobe Premiere Pro versionOpen Premiere Pro, go to Help > About Adobe Premiere Pro, or check via Creative Cloud desktop app under the Installed apps sectionAffected if Version displayed is 24.0 (any minor update) or 23.6.x and earlier
-
Confirm exact version number via systemOn Windows, check Program Files/Adobe/Adobe Premiere Pro [version] folder or check registry under HKLM\SOFTWARE\Adobe\Premiere Pro. On macOS, check /Applications/Adobe Premiere Pro/[version].app/Contents/Info.plist for CFBundleShortVersionStringAffected if Version number shown is 24.0 or 23.6.0 through 23.0.0 (any 23.x version at 23.6 or lower)
-
Check if older installations existSearch for multiple Premiere Pro installations in Program Files (Windows) or Applications folder (macOS). Also check Creative Cloud for version historyAffected if Any installed copy of Premiere Pro is version 24.0 or 23.6/earlier
-
Assess user interaction riskReview system logs, recent file access history, or endpoint detection for any recently opened media files (.prproj, .mxf, .r3d, .braw, etc.) from untrusted sourcesAffected if Users have opened or may open untrusted media files in Premiere Pro
You are affected if Adobe Premiere Pro version 24.0 or any version 23.6 and earlier is installed on your system and users could open crafted malicious files with it.
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 patch from Adobe when released. Until then, warn users not to open untrusted media files and consider implementing application whitelisting or file type restrictions for Premiere Pro.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47058 — 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-47058 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