ChromeWeb browser · Google

CVE-2014-0497

CRITICAL · 9.8 CVSS v3.1 Published 2014-02-05

Fix available

A fix is available. Upgrade to 11.2.202.336 / 11.7.700.261 or later.

See remediation →

100/100

Remediation priority · Urgent

In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

Integer underflow in Adobe Flash Player before 11.7.700.261 and 11.8.x through 12.0.x before 12.0.0.44 on Windows and Mac OS X, and before 11.2.202.336 on Linux, allows remote attackers to execute arbitrary code via unspecified vectors.

Technical summary

dbcve analysis · high confidence

Integer underflow vulnerability in Adobe Flash Player allows remote attackers to execute arbitrary code via unspecified vectors. The flaw exists in the memory handling of the Flash Player plugin across Windows, Mac OS X, and Linux platforms before the specified patched versions.

MitigationDeploy the patched Flash Player versions (11.7.700.261+, 12.0.0.44+, or 11.2.202.336+ depending on platform) or remove Flash Player if no longer required, as the CVSS 9.8 indicates trivial network exploitation with complete system compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 32.0.1700.107

Enterprise Linux DesktopOperating system

Affected:= 5.0= 6.0

Enterprise Linux EusOperating system

Affected:= 6.5

Enterprise Linux ServerOperating system

Affected:= 5.0= 6.0

Enterprise Linux Server AusOperating system

Affected:= 6.5

Enterprise Linux WorkstationOperating system

Affected:= 5.0= 6.0

Flash PlayerApplication

Affected:< 11.2.202.336< 11.7.700.261>= 11.8.800.94, < 12.0.0.44

OpensuseOperating system

Affected:= 11.4= 12.3= 13.1

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check if Adobe Flash Player is installed

On Windows: look in C:\Windows\System32\Macromed\Flash\ or check registry key HKLM\SOFTWARE\Macromedia\FlashPlayer. On Linux: check /usr/lib/flash-plugin/ or /usr/lib64/flash-plugin/. On Mac: check /Library/Internet\ Plug-Ins/Flash\ Player.plugin

Affected if The Flash plugin directory or registry key exists and contains Flash files
Determine the installed Flash Player version on Windows

Open command prompt and run: reg query "HKLM\SOFTWARE\Macromedia\FlashPlayer" /v Version, or check the file version of the DLL at C:\Windows\System32\Macromed\Flash\Flash*.ocx

Affected if The reported version matches any of the vulnerable ranges: < 11.2.202.336, < 11.7.700.261, or >= 11.8.800.94 but < 12.0.0.44
Determine the installed Flash Player version on Linux

Run: rpm -q flash-player or check the version file in the Flash plugin directory such as /usr/lib/flash-plugin/version

Affected if The reported version matches any of the vulnerable ranges: < 11.2.202.336, < 11.7.700.261, or >= 11.8.800.94 but < 12.0.0.44
Check Flash Player version in Google Chrome

Navigate to chrome://plugins in the Chrome browser URL bar, locate the Adobe Flash Player entry, and note the version number shown

Affected if The Flash version shown is < 32.0.1700.107 (Chrome bundles its own Flash)
Check Adobe Flash Player version on Mac OS X

Navigate to System Preferences > Flash Player > Advanced tab, or list the version in /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info.plist

Affected if The version matches any of the vulnerable ranges: < 11.2.202.336, < 11.7.700.261, or >= 11.8.800.94 but < 12.0.0.44

A user is affected if Adobe Flash Player or the Chrome-bundled Flash is present and its version falls within any of the vulnerable version ranges listed in the CVE.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 11.2.202.336 / 11.7.700.261 / 12.0.0.44 or later

Fixed in 11.2.202.33611.7.700.26112.0.0.44

Vendor patch helpx.adobe.com →

Interim mitigation

Deploy the patched Flash Player versions (11.7.700.261+, 12.0.0.44+, or 11.2.202.336+ depending on platform) or remove Flash Player if no longer required, as the CVSS 9.8 indicates trivial network exploitation with complete system compromise.

Recommended fix High confidence

Adobe Flash Player 12.0.0.44+ (Windows/Mac) / 11.2.202.336+ (Linux); Google Chrome 32.0.1700.107+; Chrome/Chromium users on Enterprise Linux should update via system package manager

1. Identify the installed Adobe Flash Player version by navigating to 'about:plugins' in the browser or checking 'Add/Remove Programs'
2. For Windows/Mac systems: Upgrade Adobe Flash Player to version 12.0.0.44 or later (or at minimum 11.7.700.261)
3. For Linux systems: Upgrade Adobe Flash Player to version 11.2.202.336 or later
4. For Google Chrome users: Upgrade Chrome to version 32.0.1700.107 or later (Chrome includes bundled Flash)
5. For Enterprise Linux systems (RHEL 5.x/6.x): Run 'yum update flash-plugin' or check Red Hat Network for applicable errata RHSA-2014:0022 or similar
6. For OpenSUSE systems: Apply security updates via 'zypper patch' or install updated flash-player packages from OpenSUSE security repositories
7. Restart all browsers and verify the Flash Player version via 'about:plugins'

Caveat Flash Player 12.x removed NPAPI support for some older systems; some legacy Flash content may require 11.7.x branch instead of 12.x

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

Fix this in Chrome Exploited in the wild — priority engagement

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get it fixed fast

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

helpx.adobe.comPatch / commit
www.exploit-db.comProof of Concept
helpx.adobe.comBroken LinkPatchVendor Advisory
rhn.redhat.comThird Party Advisory
secunia.comBroken LinkThird Party Advisory
secunia.comBroken LinkThird Party Advisory
secunia.comBroken LinkThird Party Advisory
secunia.comBroken LinkThird Party Advisory
secunia.comBroken LinkThird Party Advisory
www.exploit-db.comThird Party AdvisoryVDB Entry
www.securityfocus.comBroken LinkThird Party AdvisoryVDB Entry
www.securitytracker.comBroken LinkThird Party AdvisoryVDB Entry
exchange.xforce.ibmcloud.comThird Party AdvisoryVDB Entry
googlechromereleases.blogspot.comRelease Notes
lists.opensuse.orgMailing List
lists.opensuse.orgMailing List
lists.opensuse.orgMailing List
www.osvdb.orgBroken Link
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0497 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2014-0497?

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.

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

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2024-10-08

A fix existsUpgrade to 11.2.202.336 / 11.7.700.261 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 99.9%

Affects: Chrome

Remediation

Being exploited — close it fast

Fix this in Chrome 18 hrs · Moderate

Typical engagement from $3,200

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References