dbcve.org
IndesignApplication · Adobe

CVE-2018-4928

HIGH · 7.8 CVSS v3.0 Published 2018-05-19
Fix available
A fix is available. Upgrade to after 13.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe InDesign versions 13.0 and below have an exploitable Memory corruption vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe InDesign versions 13.0 and below contain a memory corruption vulnerability that can be exploited to achieve arbitrary code execution in the context of the current user.

MitigationUpdate Adobe InDesign to the latest patched version to remediate the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IndesignApplication
Affected:<= 13.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe InDesign is installed
    Check for InDesign installation by searching common program directories (Windows: C:\Program Files\Adobe\Adobe InDesign CC or similar; macOS: /Applications/Adobe InDesign CC*) or query the system registry for Adobe InDesign entries
    Affected if Adobe InDesign is found on the system
  2. Determine the installed InDesign version
    Open Adobe InDesign and navigate to Help > About Adobe InDesign, or right-click the InDesign executable and select Properties > Details to view the version number
    Affected if The displayed version is 13.0 or any version lower than 13.0
  3. Check for all InDesign installations
    If multiple versions or instances of InDesign exist (including older CC releases), verify the version of each installation individually as the vulnerability affects all versions 13.0 and below
    Affected if Any installed instance is version 13.0 or below
  4. Confirm the vulnerability applies regardless of configuration
    Note that this is a memory corruption vulnerability in the core application code that can be exploited through malicious files or data processed by InDesign - no specific feature toggle needs to be enabled for the system to be affected
    Affected if Adobe InDesign version 13.0 or below is installed and the application processes external content

The environment is affected if Adobe InDesign version 13.0 or any earlier version is installed, regardless of specific configuration settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 13.0
Interim mitigation

Update Adobe InDesign to the latest patched version to remediate the vulnerability.

Fix this in Indesign Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-4928 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-4928 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data