dbcve.org
Premiere RushApplication · Adobe

CVE-2021-43747

HIGH · 7.8 CVSS v3.1 Published 2021-12-20
Fix available
A fix is available. Upgrade to after 1.5.16 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 Rush version 1.5.16 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious WAV file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required to exploit this vulnerability.

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 confidence

Adobe Premiere Rush versions 1.5.16 and earlier contain a memory corruption vulnerability when parsing WAV audio files. The application insecurely handles malicious WAV file structures, allowing an attacker to achieve arbitrary code execution within the context of the current user session.

MitigationUpdate Adobe Premiere Rush to version 1.5.16 or later. Until patched, avoid opening WAV 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 RushApplication
Affected:<= 1.5.16

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. Confirm Adobe Premiere Rush installation
    Open the Applications folder (macOS) or Program Files (Windows) and look for Adobe Premiere Rush, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' (Windows) or 'ls /Applications | grep -i rush' (macOS)
    Affected if Adobe Premiere Rush is not installed on the system
  2. Identify installed Premiere Rush version
    On Windows, open Premiere Rush, go to Help > About Premiere Rush to view the version number. On macOS, right-click Premiere Rush in Applications, select Get Info, and check the Version field. Alternatively, check the uninstall registry key or app manifest for the exact version string.
    Affected if The version cannot be determined or the application is installed but version is unknown
  3. Compare version against affected range
    Compare the installed version number to the affected range: version 1.5.16 or earlier. Note that version 1.5.16 itself is also affected according to the CVE (versions 1.5.16 and earlier).
    Affected if Installed version is 1.5.16 or any earlier version (for example, 1.5.15, 1.5.0, 1.0, etc.)
  4. Verify WAV file import capability
    Open Premiere Rush and attempt to import a WAV audio file by going to File > Import and selecting a WAV file, or check if the application has any WAV-related import or media ingestion modules loaded.
    Affected if WAV file import functionality exists and is accessible in the installed version (which is true for all standard installations)

A user is affected if Adobe Premiere Rush is installed with version 1.5.16 or any earlier version and the application can import WAV audio files.

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 1.5.16
Interim mitigation

Update Adobe Premiere Rush to version 1.5.16 or later. Until patched, avoid opening WAV files from untrusted or unknown sources.

Recommended fix Moderate confidence

Update to the latest available Premiere Rush version (ensure version is greater than 1.5.16)

  1. Verify current Adobe Premiere Rush version by opening the application and navigating to Help > About Premiere Rush
  2. Download the latest version of Adobe Premiere Rush from the official Adobe website at adobe.com
  3. Close any running instances of Premiere Rush
  4. Run the Adobe installer and follow the prompts to update Premiere Rush to the latest version
  5. After installation, restart your computer to ensure all components are properly updated
  6. Launch Premiere Rush and confirm the version is updated by checking Help > About Premiere Rush
Caveat Adobe updates typically include new features and may have minor UI changes; review Adobe's release notes for the specific version

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

Fix this in Premiere Rush Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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