CVE-2019-7931
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 CC versions 13.1.2 and earlier have an insecure library loading (dll hijacking) vulnerability. Successful exploitation could lead to arbitrary code execution.
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 CC versions 13.1.2 and earlier are vulnerable to DLL hijacking, where the application insecurely loads dynamic link libraries from locations that can be controlled by attackers, potentially allowing 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<= 13.1.2CVSS 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.0/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.
-
Locate installed Adobe Premiere Pro CC versionOpen Adobe Premiere Pro CC, go to Help > About Adobe Premiere Pro CC to display the version number. Alternatively, check the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Premiere Pro\[Version] or HKEY_CURRENT_USER\SOFTWARE\Adobe\Premiere Pro\[Version] where [Version] is the installed version folder.Affected if The displayed version number is 13.1.2 or lower (for example 13.0, 13.1, 13.1.1, 13.1.2).
-
Verify the specific build numberIn the About dialog, note the full build number (for example, 9.0.0 or similar four-digit build). Compare this against known affected builds for version 13.1.2 and earlier.Affected if The build corresponds to a release dated on or before the 13.1.2 release.
-
Confirm application launch locationRight-click the Adobe Premiere Pro CC shortcut or executable and select Properties. Check the 'Start in' field or the path where the .exe resides.Affected if The application executable is launched from a user-controlled or untrusted directory (for example, a network share, downloads folder, or removable media).
A user is affected if Adobe Premiere Pro CC version is 13.1.2 or earlier AND the application is launched from a directory controlled by an untrusted user, allowing potential DLL hijacking.
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 dataUpdate Adobe Premiere Pro CC to a version later than 13.1.2. As a workaround, ensure the application is run from trusted directories and avoid placing the executable in user-controlled locations.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7931 — 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-2019-7931 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