Security readout for executives and security teams
Plain-English summary
This flaw lets a malicious file opened in Adobe Premiere Pro run code as the logged-in user. It is not a remote network worm scenario, but it can compromise workstations if staff open untrusted media or project files. The provided sources do not show active exploitation.
Executive priority
Treat as high priority for teams using Premiere Pro with external content workflows. It needs user interaction, but successful exploitation could compromise a workstation and business data under the current user's access.
Technical view
CVE-2021-35997 is a memory corruption issue in Adobe Premiere Pro 15.2 and earlier during crafted file parsing. CVSS 3.1 is 7.8, with local attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. CWE-788 is listed.
Likely exposure
Exposure is mainly creative, marketing, production, and contractor workstations that use Adobe Premiere Pro 15.2 or earlier. Risk rises where users receive project or media files from external parties.
Exploitation context
The source bundle says exploitation requires user interaction: a victim must open a malicious file. No KEV listing is present, and the provided sources do not cite active exploitation.
Researcher notes
The key constraints are AV:L and UI:R, so validation should focus on installed versions and file-handling exposure. The bundle does not provide proof-of-concept status, exploit telemetry, or detailed patched-version data beyond the Adobe advisory reference.
Mitigation direction
- Inventory Adobe Premiere Pro installations and identify versions 15.2 or earlier.
- Review Adobe APSB21-56 and apply the vendor-recommended update or mitigation.
- Limit opening Premiere-related files from untrusted external sources.
- Use endpoint controls to reduce impact from code execution under user context.
Validation and detection
- Confirm installed Premiere Pro versions across managed endpoints.
- Verify remediation status against Adobe APSB21-56 guidance.
- Check whether exposed teams receive external media or project files.
- Review endpoint telemetry for suspicious file-open events if risk is elevated.
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-35997 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_pro/apsb21-56.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.