Digital EditionsApplication · Adobe

CVE-2017-3093

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-20
Fix available
A fix is available. Upgrade to after 4.5.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Digital Editions versions 4.5.4 and earlier have an exploitable memory corruption vulnerability in the bitmap representation module. Successful exploitation could lead to arbitrary code execution.

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 Digital Editions versions 4.5.4 and earlier contain a memory corruption vulnerability in the bitmap representation module that can be exploited to achieve arbitrary code execution, rated critical due to the high CVSS score and potential for complete system compromise.

MitigationUpgrade Adobe Digital Editions to a version newer than 4.5.4; if immediate patching is not possible, restrict usage of the application and monitor for suspicious activity involving the software.

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
Digital EditionsApplication
Affected:<= 4.5.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 Digital Editions is installed
    Check for the presence of Adobe Digital Editions in your system's installed applications (Windows: Add/Remove Programs or Settings > Apps & features; Mac: Applications folder or Launchpad)
    Affected if Adobe Digital Editions is present on the system
  2. Identify the installed version number
    Open Adobe Digital Editions, then go to Help > About Adobe Digital Editions to display the exact version number, or right-click the executable file (ade.exe on Windows) and view Properties > Details for the File Version
    Affected if Version displayed is 4.5.4 or any version number lower than 4.5.4
  3. Confirm the bitmap module is in use
    This vulnerability affects the bitmap representation module. The flaw is triggered when processing bitmap content within e-books. No specific configuration check is needed; the vulnerability exists in the core application code for affected versions
    Affected if The installed version is 4.5.4 or earlier regardless of configuration

A user is affected if Adobe Digital Editions version 4.5.4 or any earlier version (such as 4.5.3, 4.5.2, etc.) is installed on their system

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.5.4
Interim mitigation

Upgrade Adobe Digital Editions to a version newer than 4.5.4; if immediate patching is not possible, restrict usage of the application and monitor for suspicious activity involving the software.

Recommended fix High confidence

Adobe Digital Editions 4.5.5 or later

  1. 1. Back up any important data or e-books in your current Adobe Digital Editions installation
  2. 2. Uninstall Adobe Digital Editions version 4.5.4 or earlier from your system
  3. 3. Download Adobe Digital Editions version 4.5.5 or later from the official Adobe website (get.adobe.com/digitaleditions)
  4. 4. Install the downloaded version of Adobe Digital Editions
  5. 5. Verify the installed version by checking Help > About Adobe Digital Editions
Caveat Minor - the upgrade should preserve your library data; however, re-authorization may be required for Adobe ID linked e-books

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Editions Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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