LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43012: Adobe Prelude M4A file memory corruption vulnerability could lead to remote code execution

Adobe Prelude version 10.1 (and earlier) are affected by a memory corruption vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious M4A file.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious audio file could make Adobe Prelude run attacker-controlled code when a user opens it. The attacker does not need an account, but must convince a user to open a crafted M4A file. Impact is limited to the user's permissions, but confidentiality, integrity, and availability are all rated high.

Executive priority

Treat this as a high-priority endpoint remediation item, especially for creative, media, or marketing teams that handle outside audio files. It is not shown as actively exploited in the supplied evidence, but the potential result is full code execution as the user.

Technical view

CVE-2021-43012 is a CWE-788 memory corruption flaw in Adobe Prelude 10.1 and earlier. The CVSS 3.1 score is 7.8 with local attack vector, low complexity, no privileges, and required user interaction. Successful exploitation can execute arbitrary code as the current user.

Likely exposure

Exposure is likely on endpoints where Adobe Prelude 10.1 or earlier is installed and users can receive or open untrusted M4A files. The bundle does not identify server-side exposure, Cloudflare exposure, or other Adobe products as affected.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires social engineering or another delivery path that leads a victim to open a malicious M4A file in the affected application.

Researcher notes

Evidence supports only Adobe Prelude 10.1 and earlier. The source bundle names memory corruption and CWE-788 but does not provide root-cause details, proof-of-concept material, exploit telemetry, or a specific fixed version. Avoid assuming other Adobe media tools are affected.

Mitigation direction

  • Inventory endpoints for Adobe Prelude 10.1 or earlier.
  • Review Adobe APSB21-96 for the vendor-approved update or mitigation.
  • Prioritize remediation on workstations handling external media files.
  • Limit opening of untrusted M4A files until remediation is complete.
  • Remove Adobe Prelude where it is no longer business-required.

Validation and detection

  • Confirm installed Adobe Prelude versions on managed endpoints.
  • Verify remediated systems are no longer running version 10.1 or earlier.
  • Check media-handling workflows for untrusted M4A file intake.
  • Review EDR alerts for suspicious activity from Prelude processes.
  • Document exceptions and compensating controls for any remaining installs.
Prepared
Confidence
high
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-43012 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-43012Attack 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
AdobePreludeunspecified, 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.