CVE-2024-34123
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 · uneditedPremiere Pro versions 23.6.5, 24.4.1 and earlier are affected by an Untrusted Search Path vulnerability that could lead to arbitrary code execution. An attacker could exploit this vulnerability by inserting a malicious file into the search path, which the application might execute instead of the legitimate file. This could occur when the application uses a search path to locate executables or libraries. Exploitation of this issue requires user interaction, attack complexity is high.
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 23.6.5, 24.4.1 and earlier are vulnerable to an untrusted search path issue where an attacker can place malicious executables or libraries in directories that Premiere Pro searches when locating files. When the application searches for a legitimate file, it may find and execute the attacker's file instead, leading to arbitrary 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< 23.6.7>= 24.0, < 24.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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 Adobe Premiere Pro, go to Help > About Adobe Premiere Pro, or open Creative Cloud desktop app and check the installed apps section. The version number is displayed as XX.X.X (for example 23.6.5 or 24.4.1).Affected if The version is 23.6.5 or earlier, or is 24.0 through 24.4.1 (or any version < 23.6.7 or >= 24.0 but < 24.5).
-
Confirm precise version numberIf the About screen shows only a major version (like 23 or 24), verify the full minor version in the Creative Cloud app or Windows Programs and Features / macOS Applications list. Adobe sometimes lists sub-version numbers differently depending on where you look.Affected if The precise version falls within the affected ranges: < 23.6.7 or >= 24.0 and < 24.5.
-
Verify application launch contextObserve which directory Premiere Pro is launched from. Check if the working directory (where you double-click project files or launch the app) is a shared or network location accessible to untrusted parties, or a folder where others can write files.Affected if Premiere Pro is routinely launched from or opened in directories where untrusted users can drop files (such as shared network drives, downloads folder, or removable media).
You are affected if your installed Premiere Pro version is less than 23.6.7 or is 24.0 through 24.4.1, and you work in directories where untrusted files could be placed in the application search path.
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 · scoped23.6.724.5
Update Premiere Pro to the latest patched version when available. In the interim, ensure Premiere Pro is launched only from trusted directories and avoid working in folders where untrusted parties could inject files into the application search path.
Premiere Pro 23.6.7 (for 23.x branch) or Premiere Pro 24.5+ (for 24.x branch)
- 1. Open Adobe Creative Cloud desktop application or check for updates within Premiere Pro
- 2. Navigate to Help > Check for Updates or use the Creative Cloud app to update Premiere Pro
- 3. If using version 23.x, update to version 23.6.7 or later
- 4. If using version 24.x, update to version 24.5 or later
- 5. Restart Premiere Pro after the update completes
- 6. Verify the installed version by going to Help > About Adobe Premiere Pro
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34123 — 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-2024-34123 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