Security readout for executives and security teams
Plain-English summary
Adobe Premiere Rush 1.5.16 and earlier can be compromised if a user opens a malicious WAV file. Successful exploitation could let an attacker run code as that user, risking data theft, tampering, or workstation disruption.
Executive priority
Prioritize remediation for creative, marketing, and production workstations that handle outside media. Business urgency is high where users routinely process client-supplied audio files.
Technical view
The CVE describes memory corruption in Adobe Premiere Rush WAV handling, mapped to CWE-788. CVSS 3.1 is 7.8 with local attack vector, low complexity, no privileges, required user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to systems with Adobe Premiere Rush 1.5.16 or earlier, especially users who import or open WAV files from external, client, or untrusted sources.
Exploitation context
User interaction is required. The provided sources do not show CISA KEV listing or other evidence of active exploitation, so active exploitation should not be assumed.
Researcher notes
Do not treat this as a network-reachable service flaw. Validation should focus on installed version, file-ingestion paths, user exposure, and whether Adobe’s advisory remediation has been applied.
Mitigation direction
- Identify Adobe Premiere Rush installations and versions.
- Follow Adobe APSB21-101 guidance for updates or vendor-directed remediation.
- Avoid opening WAV files from untrusted or unexpected sources.
- Run media-editing workstations with least-privilege user accounts.
- Use endpoint detection to monitor abnormal Premiere Rush child processes.
Validation and detection
- Confirm whether Premiere Rush version is 1.5.16 or earlier.
- Verify remediation status against Adobe APSB21-101.
- Review workflows that accept third-party WAV files.
- Check endpoint telemetry for unusual activity around media-file handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-788: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-43747 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://helpx.adobe.com/security/products/premiere_rush/apsb21-101.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Access of Memory Location After End of Buffer
Access of Memory Location After End of Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.