LiveActive security incident?Get immediate response
CVE Record

CVE-2022-28845: Adobe Bridge Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability

Adobe Bridge version 12.0.1 (and earlier versions) is affected by an out-of-bounds write vulnerability that could result in 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

Adobe Bridge 12.0.1 and earlier can be compromised if a user opens a malicious file. The flaw can let attacker-controlled code run with the victim user’s privileges, affecting confidentiality, integrity, and availability on that workstation.

Executive priority

Treat this as a high-priority workstation remediation item for creative teams. It requires user interaction, which lowers urgency compared with wormable flaws, but successful exploitation can give full user-context code execution.

Technical view

CVE-2022-28845 is a CWE-787 out-of-bounds write in Adobe Bridge font parsing. CVSS 3.0 is 7.8 with local attack vector, low complexity, no privileges required, and required user interaction. Successful exploitation could execute arbitrary code as the current user.

Likely exposure

Exposure is mainly desktop systems running Adobe Bridge 12.0.1 or earlier, especially creative or asset-management workflows that open files from external parties. This is not described as a network-reachable server issue.

Exploitation context

The source says exploitation requires a victim to open a malicious file. The CVE is not marked as CISA KEV in the provided bundle, and no cited source here establishes active exploitation.

Researcher notes

The provided evidence identifies the weakness class, affected product line, CVSS vector, and user-interaction requirement. It does not provide exploit indicators, proof-of-concept status, or a specific fixed version, so validation should remain inventory- and advisory-driven.

Mitigation direction

  • Inventory endpoints for Adobe Bridge 12.0.1 and earlier.
  • Check Adobe APSB22-25 for the vendor-supported remediation path.
  • Prioritize remediation for users handling external media, fonts, or creative assets.
  • Warn users not to open unexpected Bridge-compatible files from untrusted sources.
  • Use endpoint protections to monitor suspicious child processes from Adobe Bridge.

Validation and detection

  • Confirm installed Adobe Bridge versions across managed endpoints.
  • Verify whether any installations are 12.0.1 or earlier.
  • Document remediation status against Adobe APSB22-25 guidance.
  • Review asset-handling workflows for untrusted file intake.
  • Check security telemetry for suspicious activity spawned by Adobe Bridge.
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-787: 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-2022-28845 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
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.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-2022-28845Attack 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-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.