CVE-2015-3048
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 · uneditedBuffer overflow in Adobe Reader and Acrobat 10.x before 10.1.14 and 11.x before 11.0.11 on Windows and OS X allows attackers to execute arbitrary code via unknown vectors.
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 confidenceBuffer overflow vulnerability in Adobe Reader and Acrobat versions 10.x before 10.1.14 and 11.x before 11.0.11 on Windows and OS X platforms allows remote attackers to execute arbitrary code via unspecified vectors.
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= 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.11all versionsall versions= 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.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Acrobat or Reader is installedOn Windows, check Programs and Features or look for Acrobat/Adobe Reader in the installation directory. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.Affected if Either Adobe Acrobat or Adobe Reader is present on the system
-
Determine the installed Adobe versionOn Windows, right-click the Adobe 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 field. Alternatively, open Adobe Reader/Acrobat and go to Help > About Adobe Acrobat/Reader.Affected if The version cannot be determined or the product is installed
-
Compare installed version against the vulnerable 10.1.x rangeCheck if the installed version starts with 10.1.x. The affected versions are 10.1.0 through 10.1.11 inclusive (as listed in the affected products).Affected if Installed version is 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
-
Check if running on Windows or OS XIdentify the operating system using System Properties on Windows or About This Mac on macOS.Affected if The system is running Windows or macOS (the vulnerability affects both platforms)
-
Confirm JavaScript or certain features are enabledIn Adobe Reader/Acrobat, go to Edit > Preferences > Security (Enhanced) and check if protected mode or sandbox is disabled, or check if JavaScript is enabled in Edit > Preferences > JavaScript.Affected if JavaScript is enabled or protected mode/sandbox is disabled (the vulnerability can be triggered through unspecified vectors including potentially JavaScript)
A user is affected if Adobe Acrobat or Reader version 10.1.0 through 10.1.11 is installed on Windows or macOS and the system can process untrusted PDF documents.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor patches immediately by updating Adobe Reader/Acrobat to version 10.1.14 or later (for 10.x) and 11.0.11 or later (for 11.x), or migrate to newer supported versions.
Adobe Acrobat/Reader 10.1.14+ (for 10.x users) or 11.0.11+ (for 11.x users) - or migrate to latest current version
- 1. Navigate to the Adobe Acrobat/Reader download page or use your existing installation's update feature
- 2. Download the latest version of Adobe Acrobat or Adobe Reader
- 3. If using version 10.x, ensure you upgrade to version 10.1.14 or later
- 4. If using version 11.x, ensure you upgrade to version 11.0.11 or later
- 5. Close all Adobe applications before installing the update
- 6. Run the installer and follow the prompts to complete the upgrade
- 7. Restart your computer after installation completes
- 8. Verify the installed version by going to Help > About Adobe Acrobat/Reader
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2015-3048 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3048 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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