LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21092: Adobe Bridge DCM File Parsing Memory Corruption could lead to arbitrary code execution

Adobe Bridge versions 10.1.1 (and earlier) and 11.0.1 (and earlier) are affected by a memory corruption vulnerability when parsing a specially crafted file. 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 file.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-21092 is a high-severity Adobe Bridge file-parsing flaw. If a user opens a malicious DCM file, an attacker could run code with that user’s permissions. The main business risk is compromise of workstations used in creative or media workflows, especially where files arrive from outside parties.

Executive priority

Treat as a priority endpoint remediation issue, not an internet-edge emergency. The vulnerability can lead to full user-context code execution, but it requires user interaction and the provided evidence does not establish active exploitation.

Technical view

Adobe Bridge 10.1.1 and earlier, and 11.0.1 and earlier, have a memory corruption vulnerability during specially crafted file parsing. The CVSS 3.0 score is 7.8 with local attack vector, no privileges required, and required user interaction. CWE-788 is listed, indicating access outside intended memory bounds.

Likely exposure

Exposure is likely limited to endpoints with affected Adobe Bridge versions installed. Risk is higher for teams that regularly open externally supplied image, media, or DCM-related files in Bridge.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires social engineering or another delivery path that persuades a user to open a malicious file.

Researcher notes

Focus validation on version exposure and file-handling paths. The source bundle identifies memory corruption, CWE-788, and arbitrary code execution, but does not provide exploit details or enough evidence to claim active exploitation.

Mitigation direction

  • Inventory Adobe Bridge installations and versions across managed endpoints.
  • Prioritize systems running Bridge 10.1.1 or earlier, or 11.0.1 or earlier.
  • Apply Adobe’s guidance from APSB21-23 for fixed or supported versions.
  • Limit opening untrusted DCM files until affected systems are remediated.
  • Remove Adobe Bridge where it is not business-required.

Validation and detection

  • Confirm endpoint software inventory includes Adobe Bridge version data.
  • Check whether affected versions remain on user workstations.
  • Verify remediation against Adobe APSB21-23, not just package deployment status.
  • Review email, download, and file-sharing controls for suspicious DCM file delivery.
  • Document any compensating controls for systems that cannot be updated promptly.
Prepared
Confidence
high
Sources
4

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-21092 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.0)
Known Exploited
No
Published

Vector: CVSS:3.0/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
3Source 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.0HighCVSS:3.0/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.0 score

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

Vector: CVSS:3.0/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
AdobeBridgeunspecified, unspecified, 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.