LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30652: Adobe InCopy SVG File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability

Adobe InCopy versions 17.2 (and earlier) and 16.4.1 (and earlier) are 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

This Adobe InCopy flaw can let a malicious file run code on a user's computer if the user opens it. Business risk is highest where staff use InCopy to process external or untrusted design files. The supplied sources do not show active exploitation.

Executive priority

Treat as a high-priority endpoint remediation for teams using InCopy with external files. It is not internet-wormable based on supplied evidence, but compromise could give an attacker the user's workstation permissions after a malicious file is opened.

Technical view

CVE-2022-30652 is a CWE-787 out-of-bounds write in Adobe InCopy SVG file parsing. Affected versions are InCopy 17.2 and earlier, and 16.4.1 and earlier. Successful exploitation could execute arbitrary code as the current user and requires user interaction.

Likely exposure

Exposure is likely limited to endpoints with Adobe InCopy 17.2 or earlier, or 16.4.1 or earlier. Risk increases for publishing, marketing, or design workflows that open files from clients, partners, email, or web downloads.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. The sources state exploitation requires the victim to open a malicious file. No supplied source confirms public exploitation, weaponized exploit availability, or observed attacks.

Researcher notes

The record identifies local attack vector, low complexity, no privileges, required user interaction, and high confidentiality, integrity, and availability impact. Evidence is incomplete for exact fixed versions in the supplied bundle; rely on Adobe APSB22-29 for remediation specifics.

Mitigation direction

  • Inventory endpoints for Adobe InCopy installations and versions.
  • Check Adobe APSB22-29 for vendor update guidance and fixed builds.
  • Update or remove affected InCopy versions where vendor guidance applies.
  • Reduce opening of untrusted SVG or InCopy files until remediated.
  • Run InCopy with least-privileged user accounts where feasible.

Validation and detection

  • Confirm installed InCopy versions are not 17.2 or earlier, or 16.4.1 or earlier.
  • Review software inventory for unmanaged Adobe InCopy installations.
  • Identify teams that open externally supplied publishing or design files.
  • Confirm Adobe APSB22-29 guidance has been applied.
  • Monitor endpoints for suspicious InCopy-launched processes after file opens.
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-30652 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-30652Attack 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-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.