CVE-2021-43748
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 Rush versions 1.5.16 (and earlier) are affected by a Null pointer dereference vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve an application denial-of-service 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 · moderate confidenceA null pointer dereference vulnerability in Adobe Premiere Rush versions 1.5.16 and earlier allows unauthenticated attackers to cause a denial-of-service condition by tricking users into opening specially crafted malicious files.
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<= 1.5.16CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Adobe Premiere Rush installationCheck common installation paths: Windows typically at C:\Program Files\Adobe\Adobe Premiere Rush or via Windows Apps & Features. On macOS, check /Applications/Adobe Premiere Rush/. You can also search for 'Adobe Premiere Rush' in the system search.Affected if Application is installed on the system
-
Determine installed version numberRight-click the Premiere Rush application and select Properties (Windows) or Get Info (macOS). Alternatively, open Premiere Rush and go to Help > About Adobe Premiere Rush to view the exact version number.Affected if Version displayed is 1.5.16 or earlier (for example, 1.5.16, 1.5.12, 1.0.5, etc.)
-
Compare version against affected rangeCompare the installed version number to the affected range: any version from 1.0 through 1.5.16 is vulnerable. The patched version is 1.5.17 or later.Affected if Installed version is less than or equal to 1.5.16
-
Assess user file handling behaviorDetermine if the user routinely opens media files (video, audio, project files) in Premiere Rush, as exploitation requires the user to open a specially crafted malicious file.Affected if User opens media files from potentially untrusted sources in Premiere Rush
A user is affected if Adobe Premiere Rush version 1.5.16 or earlier is installed AND the user opens media files with the application, as the null pointer dereference triggers when processing a maliciously crafted file.
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 · scopedUpgrade to a patched version of Adobe Premiere Rush and avoid opening files from untrusted or unknown sources.
Premiere Rush version > 1.5.16 (check Adobe CC for latest available version)
- Open Adobe Creative Cloud desktop application
- Navigate to the 'Apps' section
- Find Adobe Premiere Rush in the list of installed apps
- Click on 'Update' or 'Install' next to Premiere Rush to get the latest version
- Alternatively, open Premiere Rush and go to Help > Updates to check for and install available updates
- Restart the application after the update completes
- Verify the updated version is newer than 1.5.16
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43748 — 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-2021-43748 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