LiveActive security incident?Get immediate response
CVE Record

CVE-2020-9728: Out-of-bounds memory access could lead to code execution

A memory corruption vulnerability exists in InDesign 15.1.1 (and earlier versions). Insecure handling of a malicious indd file could be abused to cause an out-of-bounds memory access, potentially resulting in code execution in the context of the current user.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity Adobe InDesign flaw. A user opening a malicious InDesign document could let attacker-controlled code run with that user's privileges. The main business risk is compromise through targeted document delivery to creative, marketing, publishing, or design staff.

Executive priority

Treat this as a workstation compromise risk for teams using InDesign. Prioritize patch verification and controls around externally received design files, but do not characterize it as actively exploited based on the supplied evidence.

Technical view

CVE-2020-9728 is a CWE-788 out-of-bounds memory access issue in Adobe InDesign 15.1.1 and earlier. The published CVSS 3.1 score is 7.8, with local attack vector, low complexity, no privileges required, and required user interaction through a malicious .indd file.

Likely exposure

Exposure is most likely on workstations running Adobe InDesign 15.1.1 or earlier, especially where users receive or open external .indd files. This is not described as remotely network-exploitable without user interaction.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires convincing a user to open a malicious InDesign document, after which code may run as the current user.

Researcher notes

Key constraints are AV:L and UI:R: the attacker needs document-opening behavior, not direct network reachability. Public data in the bundle identifies memory corruption and possible code execution, but does not provide exploit maturity, proof-of-concept status, or specific fixed versions.

Mitigation direction

  • Inventory Adobe InDesign installations and identify versions 15.1.1 or earlier.
  • Review and apply Adobe guidance in APSB20-52.
  • Limit opening of untrusted .indd files from external sources.
  • Use least-privilege accounts for users handling externally supplied design files.
  • Monitor endpoint alerts involving suspicious InDesign child processes or crashes.

Validation and detection

  • Confirm installed Adobe InDesign versions across managed endpoints.
  • Check whether vendor guidance from APSB20-52 has been applied.
  • Review email, file-sharing, and download paths for externally supplied .indd files.
  • Validate endpoint controls alert on abnormal InDesign behavior.
  • Prioritize systems used by marketing, publishing, and design teams.
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-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-2020-9728 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.1)
Known Exploited
No
Published

Vector: CVSS:3.1/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.1HighCVSS:3.1/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.1 score

7.8High
CVSS 3.1 vector shape for CVE-2020-9728Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/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
AdobeInDesignunspecified, 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.