CVE-2014-0528
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 · uneditedDouble free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.10 and 11.x before 11.0.07 on Windows and OS X allows attackers to execute arbitrary code via unspecified 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 · high confidenceA double-free memory corruption vulnerability in Adobe Reader and Acrobat 10.x before 10.1.10 and 11.x before 11.0.07 on Windows and OS X allows attackers to execute arbitrary code via specially crafted PDF files or other 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.0= 10.0.1= 10.0.2= 10.0.3= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7CVSS 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.
-
Check if Adobe Reader is installedOpen Windows Control Panel > Programs and Features, or run: wmic product where "name like 'Adobe Reader%'" get name,versionAffected if Adobe Reader appears in the installed programs list
-
Check if Adobe Acrobat is installedOpen Windows Control Panel > Programs and Features, or run: wmic product where "name like 'Adobe Acrobat%'" get name,versionAffected if Adobe Acrobat appears in the installed programs list
-
Determine the exact version of Adobe ReaderRight-click the Adobe Reader executable (typically in C:\Program Files\Adobe\Reader X\Reader\), select Properties, and view the Version tab. Or run: wmic product where "name like 'Adobe Reader%'" get versionAffected if The version number is 10.0, 10.0.1, 10.0.2, 10.0.3, 10.1, 10.1.1, 10.1.2, 10.1.3, 10.1.4, 10.1.5, 10.1.6, or 10.1.7
-
Determine the exact version of Adobe AcrobatRight-click the Adobe Acrobat executable (typically in C:\Program Files\Adobe\Acrobat X\Acrobat\), select Properties, and view the Version tab. Or run: wmic product where "name like 'Adobe Acrobat%'" get versionAffected if The version number is 10.0, 10.0.1, 10.0.2, 10.0.3, 10.1, 10.1.1, 10.1.2, 10.1.3, 10.1.4, 10.1.5, 10.1.6, or 10.1.7
Your environment is affected if Adobe Reader or Adobe Acrobat version 10.0 through 10.1.7 is installed and you open untrusted PDF files.
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 · scopedUpdate Adobe Reader and Acrobat to version 10.1.10 or later (for 10.x) and 11.0.07 or later (for 11.x) to patch the vulnerability. In enterprise environments, test the update before broad deployment to ensure compatibility with existing PDF workflows.
Adobe Reader/Acrobat 10.1.10 or later (10.x line); 11.0.07 or later (11.x line) - upgrade to latest available version
- Identify the currently installed Adobe Reader or Acrobat version via Help > About Adobe Reader/Acrobat
- Download the fixed version from Adobe's official website (helpx.adobe.com) - for 10.x line use 10.1.10 or later, for 11.x line use 11.0.07 or later
- Close all Adobe Reader or Acrobat instances
- Install the updated version using Adobe's installer or update mechanism
- Restart the application and verify the version number reflects the patched release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0528 — 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-2014-0528 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