LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34250: Adobe InCopy Font Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability

Adobe InCopy versions 17.2 (and earlier) and 16.4.1 (and earlier) are affected by a Heap-based Buffer Overflow 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

CVE-2022-34250 is a high-severity Adobe InCopy flaw. A malicious file can trigger memory corruption and run code as the user who opens it. The main business risk is compromise of workstations used for publishing or document workflows, especially where users handle external files.

Executive priority

Treat this as a targeted workstation risk, not a perimeter emergency. Prioritize users who open external content and systems with affected InCopy versions. No active exploitation is supported by the supplied evidence.

Technical view

Adobe InCopy 17.2 and earlier, and 16.4.1 and earlier, are affected by a CWE-122 heap-based buffer overflow. The CVSS 3.0 score is 7.8 with local attack vector and required user interaction. Successful exploitation could provide confidentiality, integrity, and availability impact in the current user context.

Likely exposure

Exposure is limited to systems with affected Adobe InCopy versions installed. Risk is higher for users who receive or open externally supplied files. The source bundle does not identify other Adobe products as affected.

Exploitation context

The source bundle says exploitation requires user interaction: a victim must open a malicious file. CISA KEV status is false, and the provided sources do not state active exploitation or public exploit availability.

Researcher notes

Evidence supports arbitrary code execution in the current user context through font parsing memory corruption. The bundle does not provide fixed version details, indicators of compromise, exploit samples, or confirmed exploitation. Avoid expanding scope beyond Adobe InCopy without additional vendor evidence.

Mitigation direction

  • Inventory Adobe InCopy installations and identify affected versions.
  • Consult Adobe APSB22-29 for official remediation guidance.
  • Prioritize remediation on systems handling external publishing files.
  • Restrict opening untrusted files until remediation is complete.
  • Use least privilege for users running InCopy.

Validation and detection

  • Compare installed InCopy versions against the affected ranges.
  • Confirm patch or mitigation status against Adobe APSB22-29.
  • Verify vulnerable versions are absent from managed endpoints.
  • Review whether affected users handle externally supplied files.
  • Document any systems requiring temporary compensating controls.
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-122: 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-34250 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-34250Attack 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
AdobeInCopyunspecified, unspecified, unspecifiedListed
Weakness

CWE details

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

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.