dbcve.org
ReaderApplication · Adobe

CVE-2011-4374

HIGH · 9.3 CVSS v2.0 Published 2012-01-19
Fix available
A fix is available. Upgrade to after 10.1 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
Integer overflow in Adobe Reader 9.x before 9.4.6 on Linux 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 · moderate confidence

Integer overflow vulnerability in Adobe Reader 9.x before version 9.4.6 on Linux that allows attackers to execute arbitrary code via unspecified vectors. Integer overflows can cause unexpected memory behavior leading to code execution.

MitigationUpgrade Adobe Reader to version 9.4.6 or later. If the affected software is end-of-life, consider removing it or implementing compensating controls such as restricting access to the application and monitoring for exploitation attempts.

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
ReaderApplication
Affected:>= 8.0, <= 8.3>= 10.0, <= 10.1>= 9.0.0, <= 9.4.5
AcrobatApplication
Affected:>= 8.0, <= 8.3>= 9.0, <= 9.4.5>= 10.0, <= 10.1

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

AV:N/AC:M/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. Check if Adobe Reader is installed
    Run 'which acroread' or look for /opt/Adobe/Reader* directories on Linux systems
    Affected if The command returns a path or Adobe Reader directory exists
  2. Determine installed Adobe Reader version
    Run 'acroread -version' or check the version file in the Adobe Reader installation directory
    Affected if Version output shows a number less than 9.4.6 for version 9.x, or within 8.0-8.3, or within 10.0-10.1
  3. Check if Adobe Acrobat is installed
    Run 'which acrobat' or look for Adobe Acrobat installation directories
    Affected if Acrobat is found on the system
  4. Determine installed Adobe Acrobat version
    Run 'acrobat -version' or check version through the application help about dialog
    Affected if Version shows 8.0-8.3, 9.0-9.4.5, or 10.0-10.1

The system is affected if Adobe Reader or Adobe Acrobat is installed with a version matching 8.0 through 8.3, 9.0.0 through 9.4.5, or 10.0 through 10.1 on Linux.

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

Upgrade Adobe Reader to version 9.4.6 or later. If the affected software is end-of-life, consider removing it or implementing compensating controls such as restricting access to the application and monitoring for exploitation attempts.

Recommended fix High confidence

Adobe Reader 9.4.6 or later (for 9.x versions); migrate to current supported Adobe Acrobat/Reader version (for 8.x and 10.x versions)

  1. 1. Identify the installed Adobe Reader or Acrobat version by opening the application and navigating to Help > About Adobe Reader/Acrobat
  2. 2. For Adobe Reader 9.x (9.0.0 through 9.4.5) on all platforms: Download and install Adobe Reader 9.4.6 or later from the Adobe website
  3. 3. For Adobe Acrobat 9.x (9.0 through 9.4.5): Download and install the corresponding Acrobat security update (APSb12-01 or later) from Adobe's security bulletin page
  4. 4. For Adobe Reader/Acrobat 8.x (8.0 through 8.3): These versions are end-of-life; Adobe no longer provides patches; migrate to a supported newer version
  5. 5. For Adobe Reader/Acrobat 10.x (10.0 through 10.1): These versions are end-of-life; Adobe no longer provides patches; migrate to a supported newer version
  6. 6. After upgrading, verify the new version by checking Help > About to confirm the security update was applied
  7. 7. Enable automatic updates in the application preferences to receive future security patches
Caveat Adobe Reader 8.x and Acrobat 8.x are End-of-Life with no further patches; users must migrate to newer supported versions. Adobe Reader/Acrobat 10.x are also End-of-Life.

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

Fix this in Reader Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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