dbcve.org
AcrobatApplication · Adobe

CVE-2015-3068

HIGH · 10.0 CVSS v2.0 Published 2015-05-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Reader and Acrobat 10.x before 10.1.14 and 11.x before 11.0.11 on Windows and OS X allow attackers to bypass intended restrictions on JavaScript API execution via unspecified vectors, a different vulnerability than CVE-2015-3060, CVE-2015-3061, CVE-2015-3062, CVE-2015-3063, CVE-2015-3064, CVE-2015-3065, CVE-2015-3066, CVE-2015-3067, CVE-2015-3069, CVE-2015-3071, CVE-2015-3072, CVE-2015-3073, and CVE-2015-3074.

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

Adobe Reader and Acrobat 10.x before 10.1.14 and 11.x before 11.0.11 contain a vulnerability that allows attackers to bypass intended security restrictions on JavaScript API execution. This security bypass enables unauthorized JavaScript code to run within the application context, potentially leading to arbitrary code execution. The vulnerability affects both Windows and OS X platforms.

MitigationApply the vendor-supplied patches (Adobe Reader/Acrobat 10.1.14 or 11.0.11 and later) to address this vulnerability. Alternatively, consider disabling JavaScript execution in Adobe Reader/Acrobat as a defense-in-depth measure if JavaScript functionality is not required.

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:= 10.1.0= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7= 10.1.8= 10.1.9= 10.1.10= 10.1.11
Mac Os XOperating system
Affected:all versions
WindowsOperating system
Affected:all versions
Acrobat ReaderApplication
Affected:= 10.1.0= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7= 10.1.8= 10.1.9= 10.1.10= 10.1.11

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 if Adobe Reader or Acrobat is installed
    On Windows, check the Add/Remove Programs list or look in C:\Program Files\Adobe for Acrobat or Reader folders. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.
    Affected if Adobe Reader or Adobe Acrobat software is present on the system
  2. Determine the installed Adobe product version
    On Windows, right-click the Adobe Reader/Acrobat executable, select Properties, and check the Details tab for version information. On macOS, right-click the application in /Applications, select Get Info, and check the version number.
    Affected if The version displayed matches 10.1.0 through 10.1.11, or any 11.x version before 11.0.11
  3. Confirm the exact version number for precise matching
    Open Adobe Reader or Acrobat, go to Help > About Adobe Reader/Acrobat to view the exact version string (for example: 10.1.10 or 11.0.10).
    Affected if The version is exactly 10.1.0, 10.1.1, 10.1.2, 10.1.3, 10.1.4, 10.1.5, 10.1.6, 10.1.7, 10.1.8, 10.1.9, 10.1.10, or 10.1.11, or is 11.0.10 or earlier in the 11.x line
  4. Verify JavaScript execution is enabled in the application
    In Adobe Reader/Acrobat, go to Edit > Preferences > JavaScript and check if JavaScript is enabled. On Windows, you can also check the registry key: HKEY_CURRENT_USER\Software\Adobe\Acrobat...\JSEnable (value 1 means enabled).
    Affected if JavaScript is enabled in the application settings

The environment is affected if Adobe Reader or Acrobat version 10.1.0 through 10.1.11 or any 11.x version before 11.0.11 is installed with JavaScript execution enabled.

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
Patch available Apply the vendor patch
Vendor patch helpx.adobe.com →
Interim mitigation

Apply the vendor-supplied patches (Adobe Reader/Acrobat 10.1.14 or 11.0.11 and later) to address this vulnerability. Alternatively, consider disabling JavaScript execution in Adobe Reader/Acrobat as a defense-in-depth measure if JavaScript functionality is not required.

Recommended fix High confidence

Adobe Acrobat/Reader 10.1.14 (for 10.x users) or 11.0.11 (for 11.x users) or later

  1. 1. Identify the current installed version of Adobe Acrobat or Adobe Reader by opening the application and navigating to Help > About Adobe Acrobat Reader or About Adobe Acrobat.
  2. 2. If the version is 10.x before 10.1.14 or 11.x before 11.0.11, navigate to https://get.adobe.com/reader/ or https://helpx.adobe.com/security/products/reader/apsb15-10.html to download the latest version.
  3. 3. Download the appropriate installer for your operating system (Windows or Mac OS X) and architecture.
  4. 4. Close all Adobe Acrobat or Reader instances and any applications that might be using PDF files.
  5. 5. Run the downloaded installer and follow the on-screen prompts to complete the installation.
  6. 6. After installation completes, verify the installed version is 10.1.14 or later for version 10.x, or 11.0.11 or later for version 11.x.
Caveat None documented for this security update; this is a routine security patch

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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