LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43029: Adobe Premiere Rush M4A File Memory Corruption Remote Code Execution

Adobe Premiere Rush version 1.5.16 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious M4A file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required to exploit this vulnerability.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects Adobe Premiere Rush 1.5.16 and earlier. A malicious M4A audio file could corrupt memory and let code run as the user who opens it. It requires user interaction, so business risk centers on creative workstations and users handling media from external or untrusted sources.

Executive priority

Treat this as a targeted workstation risk rather than a network-wide emergency. Prioritize teams that receive external media, because compromise could run code with the user's access and affect confidentiality, integrity, and availability on that workstation.

Technical view

CVE-2021-43029 is a CWE-788 memory corruption flaw in Adobe Premiere Rush caused by insecure handling of crafted M4A files. The CVSS 3.1 score is 7.8 with local attack vector, low complexity, no privileges required, and required user interaction. Successful exploitation may enable arbitrary code execution in the current user's context.

Likely exposure

Exposure is most likely on endpoints running Adobe Premiere Rush 1.5.16 or earlier, especially where users import or open M4A files received externally. The source bundle does not identify affected operating systems, enterprise configurations, or CPEs.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires a user to open or process a malicious M4A file, making phishing, file-sharing, and media supply workflows the relevant threat paths.

Researcher notes

The bundle supports affected version 1.5.16 and earlier, CVSS 7.8, CWE-788, required user interaction, and arbitrary code execution impact. It does not provide exploit-in-the-wild evidence, exact fixed version details, CPEs, or deeper root-cause detail beyond M4A handling memory corruption.

Mitigation direction

  • Review Adobe APSB21-101 for vendor remediation guidance and fixed versions.
  • Update Adobe Premiere Rush where Adobe provides a corrected release.
  • Prioritize creative workstations handling external media files.
  • Limit opening M4A files from untrusted sources until remediated.
  • Use endpoint controls to reduce impact of user-context code execution.

Validation and detection

  • Inventory endpoints for Adobe Premiere Rush installations.
  • Identify versions at or below 1.5.16.
  • Confirm whether Adobe APSB21-101 remediation has been applied.
  • Review email, download, and media-ingest workflows for untrusted M4A exposure.
  • Check security tooling for suspicious activity involving Premiere Rush processes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2021-43029 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-43029Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobePremiere Rushunspecified, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-788 · source CWE mapping

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.