dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 8 Oct 2024.
Enterprise Linux DesktopOperating system · Redhat

CVE-2013-0648

HIGH · 8.8 CVSS v3.1 Published 2013-02-27
Fix available
A fix is available. Upgrade to 10.3.183.67 / 11.2.202.273 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges 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
Unspecified vulnerability in the ExternalInterface ActionScript functionality in Adobe Flash Player before 10.3.183.67 and 11.x before 11.6.602.171 on Windows and Mac OS X, and before 10.3.183.67 and 11.x before 11.2.202.273 on Linux, allows remote attackers to execute arbitrary code via crafted SWF content, as exploited in the wild in February 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

This is a use-after-free vulnerability in Adobe Flash Player's ExternalInterface ActionScript API, which allows SWF files to communicate with browser JavaScript. Attackers exploit this by crafting malicious SWF content that corrupts memory, enabling arbitrary code execution on the victim's system.

MitigationUpdate Adobe Flash Player to version 10.3.183.67 or later (11.x to 11.6.602.171 on Windows/Mac, 11.2.202.273 on Linux) to remediate this vulnerability. Consider disabling Flash Player in browsers if update is not possible.

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:< 10.3.183.67>= 11.0, < 11.6.602.171>= 11.0, < 11.2.202.273
OpensuseOperating system
Affected:= 11.4= 12.1
Linux Enterprise DesktopOperating system
Affected:= 10= 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
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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, look for the Flash plugin in browser plugin directories: ls -la /usr/lib/flash-plugin/ or ls -la /usr/lib/mozilla/plugins/ | grep -i flash. On RHEL/CentOS also check /opt/adobe-flash/
    Affected if No Flash plugin files are found, then the system is not affected by this specific Flash vulnerability
  2. Determine the installed Flash Player version on Linux
    Run: rpm -q flash-plugin (RHEL/CentOS) or rpm -q flashplayer (SUSE/OpenSUSE). Alternatively, check the plugin file directly: ls -la /usr/lib/flash-plugin/libflashplayer.so and examine file version info if available
    Affected if Unable to determine version - Flash may be installed via a different method or not at all
  3. Compare your installed version against affected ranges
    Compare the version number you found against these vulnerable ranges: < 10.3.183.67, or >= 11.0.0 and < 11.6.602.171 (Windows/Mac), or >= 11.0.0 and < 11.2.202.273 (Linux). If your version falls into any of these ranges, you are affected
    Affected if Your installed version is 10.3.x before 10.3.183.67, OR 11.x before 11.6.602.171 (non-Linux) OR 11.x before 11.2.202.273 (Linux)
  4. Check which Flash Player package is installed on SUSE/OpenSUSE
    Run: rpm -qa | grep -i flash to list all flash-related packages, then use: rpm -q --qf '%{VERSION}-%{RELEASE}' <package_name> to get exact version
    Affected if The installed version matches the affected version ranges listed for OpenSUSE (11.4, 12.1) or SLED (10, 11)

You are affected if Adobe Flash Player is installed and its version falls below 10.3.183.67, or is 11.x but below 11.6.602.171 (Windows/Mac) or below 11.2.202.273 (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 10.3.183.67 / 11.2.202.273 / 11.6.602.171 or later
Fixed in 10.3.183.6711.2.202.27311.6.602.171
Vendor patch www.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 10.3.183.67 or later (11.x to 11.6.602.171 on Windows/Mac, 11.2.202.273 on Linux) to remediate this vulnerability. Consider disabling Flash Player in browsers if update is not possible.

Recommended fix High confidence

Flash Player 11.2.202.273 or later for Linux (or 10.3.183.67 for all platforms)

  1. 1. Identify the installed Flash Player version by navigating to 'About Flash Player' in the Adobe website or checking your system's software packages
  2. 2. For Red Hat Enterprise Linux systems, run 'yum update flash-plugin' or 'rpm -Uvh' with the appropriate updated Flash Player package from the Red Hat network (RHN)
  3. 3. For openSUSE systems, run 'zypper update flash-player' or install the updated package from the openSUSE repositories
  4. 4. After installation, verify the Flash Player version is at least 10.3.183.67 (or 11.2.202.273 for Linux) using 'rpm -q flash-plugin' or by checking in the browser
  5. 5. Restart any web browsers to ensure the updated Flash Player plugin is loaded
  6. 6. Consider removing Flash Player entirely if no longer needed, as Adobe ended support in December 2020
Caveat Upgrading Flash Player should not introduce breaking changes; however, some legacy content may behave differently with newer versions. Consider testing critical Flash-based applications after updating.

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

Fix this in Enterprise Linux Desktop Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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-0648 — 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-0648 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