LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30654: 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

Adobe InCopy can be compromised if a user opens a specially crafted malicious file. Successful exploitation could let an attacker run code with that user’s permissions, putting documents, credentials, and workstation integrity at risk.

Executive priority

Treat this as a high-priority endpoint remediation issue for publishing, marketing, and document-production teams. Business urgency comes from potential code execution after a single malicious file open, not from confirmed active exploitation.

Technical view

CVE-2022-30654 is a heap-based buffer overflow in Adobe InCopy font parsing. The CVSS 3.0 score is 7.8. The attack vector is local with required user interaction, no privileges required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on workstations running Adobe InCopy 17.2 or earlier, or 16.4.1 or earlier, especially where users open externally supplied design or document files.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. Exploitation requires convincing a victim to open a malicious file, so phishing or file-sharing workflows are the plausible delivery context.

Researcher notes

The evidence supports heap overflow, arbitrary code execution as the current user, affected version ranges, and required user interaction. The provided bundle does not include exploit-in-the-wild evidence, proof-of-concept details, or explicit fixed versions.

Mitigation direction

  • Inventory Adobe InCopy installations and versions across user workstations.
  • Review Adobe APSB22-29 for vendor-provided update or mitigation guidance.
  • Prioritize remediation for users handling external design or publishing files.
  • Limit opening of untrusted files until affected systems are remediated.
  • Remove InCopy from endpoints where it is not business-required.

Validation and detection

  • Confirm whether any endpoint runs InCopy 17.2 or earlier.
  • Confirm whether any endpoint runs InCopy 16.4.1 or earlier.
  • Check software management records against Adobe APSB22-29 guidance.
  • Review email and file-sharing controls for risky external file intake.
  • Document remaining exceptions and 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-30654 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-30654Attack 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.