dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-12773

HIGH · 8.8 CVSS v3.0 Published 2018-07-20
Fix available
A fix is available. Upgrade to after 18.011.20040 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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 Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Use-after-free 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 · moderate confidence

Use-after-free vulnerability in Adobe Acrobat and Reader allows attackers to manipulate freed memory objects, potentially leading to arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Acrobat and Reader to the latest patched versions beyond 2018.011.20040, 2017.011.30080, and 2015.006.30418 respectively.

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
Acrobat DcApplication
Affected:>= 15.006.30060, <= 15.006.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/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. Check if Adobe Acrobat or Reader is installed
    On Windows, open Control Panel > Programs and Features and look for 'Adobe Acrobat' or 'Adobe Acrobat Reader'. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.
    Affected if Either Adobe Acrobat Dc or Adobe Acrobat Reader Dc is installed
  2. Find the installed version number
    For Adobe Acrobat: Open the application, go to Help > About Adobe Acrobat. For Adobe Reader: Open the application, go to Help > About Adobe Reader. The version appears as a number like '15.006.30060' or '18.011.20040'. Alternatively on Windows, right-click the executable (AcroRd32.exe or AcroExch.exe) in the installation folder, select Properties, and check the Details tab for the Product Version.
    Affected if A version number is found that matches the affected ranges
  3. Compare the version against the first affected range
    Verify if the installed version falls between 15.006.30060 and 15.006.30418 inclusive. This includes versions like 15.006.30060, 15.006.30352, or 15.006.30418.
    Affected if Installed version is between 15.006.30060 and 15.006.30418 inclusive
  4. Compare the version against the second affected range
    Verify if the installed version falls between 15.008.20082 and 18.011.20040 inclusive. This includes versions like 15.008.20082, 17.011.30059, or 18.011.20040.
    Affected if Installed version is between 15.008.20082 and 18.011.20040 inclusive
  5. Compare the version against the third affected range
    Verify if the installed version falls between 17.011.30059 and 17.011.30080 inclusive. This includes versions like 17.011.30059, 17.011.30070, or 17.011.30080.
    Affected if Installed version is between 17.011.30059 and 17.011.30080 inclusive

If the installed Adobe Acrobat Dc or Adobe Acrobat Reader Dc version matches any of the three affected ranges (15.006.30060-15.006.30418, 15.008.20082-18.011.20040, or 17.011.30059-17.011.30080), the environment is affected by CVE-2018-12773.

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

Update Adobe Acrobat and Reader to the latest patched versions beyond 2018.011.20040, 2017.011.30080, and 2015.006.30418 respectively.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,650
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12773 — 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-12773 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