AcrobatApplication · Adobe

CVE-2020-24437

HIGH · 7.8 CVSS v3.1 Published 2020-11-05
Fix available
A fix is available. Upgrade to after 20.012.20048 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
Acrobat Reader DC versions 2020.012.20048 (and earlier), 2020.001.30005 (and earlier) and 2017.011.30175 (and earlier) are affected by a use-after-free vulnerability in the processing of Format event actions 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.

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

A use-after-free vulnerability exists in Adobe Acrobat Reader DC's processing of Format event actions. When processing these events, memory is freed but the application continues using the dangling pointer, potentially allowing arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Acrobat Reader DC to a version later than 2020.012.20048, 2020.001.30005, or 2017.011.30175 (depending on the track). Avoid opening untrusted PDF files until the update is applied.

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
AcrobatApplication
Affected:<= 20.001.30005
Acrobat DcApplication
Affected:<= 17.011.30175<= 20.012.20048
Acrobat ReaderApplication
Affected:<= 20.001.30005
Acrobat Reader DcApplication
Affected:<= 17.011.30175<= 20.012.20048

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.1/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. Identify installed Adobe product and version
    Open Adobe Acrobat Reader or Adobe Acrobat, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Alternatively, on Windows check Programs and Features or the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-A90000000001} for Reader, or similar for Acrobat. On macOS, right-click the application in Applications and select Get Info to see the version.
    Affected if Version is at or below 20.001.30005 for standard releases, or at or below 20.012.20048 / 17.011.30175 for DC track versions.
  2. Confirm product type is affected
    Determine whether the installed product is Adobe Acrobat (full), Adobe Acrobat Reader, Adobe Acrobat DC, or Adobe Acrobat Reader DC. Each has separate version ranges.
    Affected if Product is Adobe Acrobat, Adobe Acrobat Reader, Adobe Acrobat DC, or Adobe Acrobat Reader DC with version within the affected ranges.
  3. Verify Format event action processing is possible
    The vulnerability triggers when processing PDF files that contain Format event actions. This is a feature in PDF forms. Check if the user opens or processes PDF forms or untrusted PDF documents.
    Affected if User opens or processes PDF files, particularly PDF forms containing Format event actions, with an affected version.

A user is affected if they have Adobe Acrobat or Adobe Acrobat Reader (any DC or standard variant) installed at version 20.001.30005 or below, or DC versions at or below 20.012.20048 or 17.011.30175, and they open PDF files containing Format event actions.

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 20.012.20048
Interim mitigation

Update Adobe Acrobat Reader DC to a version later than 2020.012.20048, 2020.001.30005, or 2017.011.30175 (depending on the track). Avoid opening untrusted PDF files until the update is applied.

Fix this in Acrobat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-24437 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