dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2014-7926

HIGH · 7.5 CVSS v2.0 Published 2015-01-22
Fix available
A fix is available. Upgrade to after 40.0.2214.85 or later.
See remediation →
84/100
Remediation priority · High
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
The Regular Expressions package in International Components for Unicode (ICU) 52 before SVN revision 292944, as used in Google Chrome before 40.0.2214.91, allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via vectors related to a zero-length quantifier.

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

A memory corruption vulnerability exists in the Regular Expressions package of International Components for Unicode (ICU) 52 before SVN revision 292944. The flaw is triggered by specially crafted regex patterns containing zero-length quantifiers, which cause improper memory handling during pattern matching. This can lead to denial of service through memory corruption and potentially enable unspecified other impact.

MitigationUpgrade ICU library to revision 292944 or later. For Chrome users, upgrade to version 40.0.2214.91 or later. If direct patching is not possible, consider input validation to reject or sanitize regex patterns with zero-length quantifiers before processing.

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 Desktop SupplementaryOperating system
Affected:= 6.0
Enterprise Linux Server SupplementaryOperating system
Affected:= 6.0
Enterprise Linux Server Supplementary EusOperating system
Affected:= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
Affected:= 6.0
ChromeWeb browser
Affected:<= 40.0.2214.85
Ubuntu LinuxOperating system
Affected:= 14.04= 14.10
OpensuseOperating system
Affected:= 13.1= 13.2
Communications Messaging ServerOperating system
Affected:= 7.0.5= 8.0

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Identify ICU library version
    Run 'icuinfo' or check package manager output: on RHEL/Ubuntu use 'rpm -q libicu' or 'dpkg -l libicu*', on SUSE use 'rpm -q libicu'. Compare the version number to ICU 52.x before the fix revision.
    Affected if The installed ICU library version is 52.x and predates the fix revision 292944 (SVN).
  2. Verify Chrome browser version
    Open Chrome, go to Settings > About Chrome, or navigate to chrome://version. Check the version number displayed.
    Affected if Chrome version is 40.0.2214.85 or earlier.
  3. Check if regex processing is in use
    Audit application logs, code, or configuration for patterns that invoke the ICU regex engine. Look for usage of ICU-based regex functions in any custom or third-party code interacting with the affected library.
    Affected if Any application or service actively uses the ICU Regular Expressions package for pattern matching.
  4. Verify Oracle Communications Messaging Server version
    Check installed version of Oracle Communications Messaging Server: examine the product installation directory, run 'pkg_info' or consult the software inventory for version 7.0.5 or 8.0.
    Affected if Oracle Communications Messaging Server versions 7.0.5 or 8.0 are installed, as these ship with the vulnerable ICU library.
  5. Confirm OS and library bundle
    Identify the operating system version (Ubuntu 14.04, 14.10; RHEL 6.x; OpenSUSE 13.1, 13.2) and check if the ICU library came bundled with the OS or with a dependent package.
    Affected if Running Ubuntu 14.04 or 14.10, RHEL 6.0/6.6, or OpenSUSE 13.1/13.2 with ICU library versions matching the affected ranges.

Your environment is affected if the ICU library version is 52.x before SVN revision 292944, or Chrome version 40.0.2214.85 or earlier, AND the regex functionality is actively used to process untrusted regex patterns.

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.

From vendor data
Upgrade available Upgrade to a release after 40.0.2214.85
Interim mitigation

Upgrade ICU library to revision 292944 or later. For Chrome users, upgrade to version 40.0.2214.91 or later. If direct patching is not possible, consider input validation to reject or sanitize regex patterns with zero-length quantifiers before processing.

Fix this in Enterprise Linux Desktop Supplementary Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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