dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2013-2555

HIGH · 10.0 CVSS v2.0 Published 2013-03-11
Fix available
A fix is available. Upgrade to 10.3.183.75 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 Flash Player before 10.3.183.75 and 11.x before 11.7.700.169 on Windows and Mac OS X, before 10.3.183.75 and 11.x before 11.2.202.280 on Linux, before 11.1.111.50 on Android 2.x and 3.x, and before 11.1.115.54 on Android 4.x; Adobe AIR before 3.7.0.1530; and Adobe AIR SDK & Compiler before 3.7.0.1530 allows remote attackers to execute arbitrary code via unspecified vectors, as demonstrated by VUPEN during a Pwn2Own competition at CanSecWest 2013.

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

Integer overflow vulnerability in Adobe Flash Player and AIR allowing remote attackers to execute arbitrary code via unspecified vectors. The flaw was demonstrated by VUPEN during the Pwn2Own competition at CanSecWest 2013, indicating active exploitation potential.

MitigationUpdate Adobe Flash Player to version 10.3.183.75+/11.7.700.169+ (Windows/Mac), 11.2.202.280+ (Linux), or 11.1.115.54+ (Android 4.x); update Adobe AIR to 3.7.0.1530 or later. Consider disabling Flash Player as a defense-in-depth measure.

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
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux EusOperating system
Affected:= 5.9= 6.4
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux Server AusOperating system
Affected:= 5.9= 6.4
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Flash PlayerApplication
Affected:<= 11.1.115.48<= 11.1.111.44>= 11.0, <= 11.6.602.180>= 11.0, <= 11.2.202.275< 10.3.183.75<= 10.3.183.75
AirApplication
Affected:<= 3.6.0.6090
OpensuseOperating system
Affected:= 11.4= 12.1= 12.2= 12.3

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. Check if Adobe Flash Player is installed
    On Linux, run: rpm -qa | grep -i flash (RHEL) or rpm -qa | grep -i flash (openSUSE). On Windows, check C:\Windows\System32\Macromed\Flash\ for flash*.ocx files.
    Affected if No Flash Player package or file is found - not affected. If found, proceed to version check.
  2. Get installed Flash Player version on Linux
    Run: rpm -q --queryformat '%{VERSION}' flash-plugin or check the NPAPI plugin file directly at /usr/lib64/flash-plugin/libflashplayer.so or /usr/lib/flash-plugin/libflashplayer.so and run: strings /usr/lib/flash-plugin/libflashplayer.so | grep "Flash Player" | head -1
    Affected if Version matches one of the vulnerable ranges: <= 11.1.115.48, <= 11.1.111.44, 11.0-11.6.602.180, 11.0-11.2.202.275, < 10.3.183.75, or <= 10.3.183.75 - AFFECTED.
  3. Get Flash Player version on Windows
    Open Control Panel > Programs > Programs and Features, look for Adobe Flash Player XX in the list, or check: reg query "HKLM\SOFTWARE\Macromedia\FlashPlayer" /v Version
    Affected if Version matches any of the vulnerable version ranges listed above - AFFECTED.
  4. Check if Adobe AIR is installed
    On Linux, run: rpm -qa | grep -i "adobe-air" or rpm -qa | grep -i "adobeAIR". On Windows, check C:\Program Files\Adobe\Adobe AIR\ or C:\Program Files (x86)\Adobe\Adobe AIR\ for the AIR application.
    Affected if Adobe AIR is installed - proceed to version check.
  5. Get Adobe AIR version
    On Linux, run: rpm -q --queryformat '%{VERSION}' adobe-air or check the installed directory. On Windows, run: msiexec /x {UUID} and look for ProductVersion in the registry at HKLM\SOFTWARE\Adobe\AIR
    Affected if Version <= 3.6.0.6090 - AFFECTED.

A system is affected if Adobe Flash Player version falls within any of the vulnerable ranges (11.x versions up to 11.6.602.180/11.2.202.275, or 10.x up to 10.3.183.75) or Adobe AIR version is 3.6.0.6090 or lower.

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 10.3.183.75 or later
Fixed in 10.3.183.75
Interim mitigation

Update Adobe Flash Player to version 10.3.183.75+/11.7.700.169+ (Windows/Mac), 11.2.202.280+ (Linux), or 11.1.115.54+ (Android 4.x); update Adobe AIR to 3.7.0.1530 or later. Consider disabling Flash Player as a defense-in-depth measure.

Recommended fix High confidence

Adobe Flash Player 11.7.700.169 (Windows/Mac), 11.2.202.280 (Linux), 11.1.111.50 (Android 2.x/3.x), 11.1.115.54 (Android 4.x); Adobe AIR 3.7.0.1530

  1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click context menu
  2. For Windows/Mac systems: Upgrade Flash Player to version 11.7.700.169 or later (11.x series), or 10.3.183.75 or later (10.3.x series)
  3. For Linux systems: Upgrade Flash Player to version 11.2.202.280 or later
  4. For Android 2.x/3.x devices: Upgrade Flash Player to version 11.1.111.50 or later
  5. For Android 4.x devices: Upgrade Flash Player to version 11.1.115.54 or later
  6. For Adobe AIR: Upgrade to version 3.7.0.1530 or later
  7. Download updates from the official Adobe product update pages or use the automated update feature
  8. Verify the installed version matches the target fixed version after update
Caveat Users on older operating systems may need to retain the 10.3.x branch if 11.x is incompatible; ensure browser compatibility after upgrading

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

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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