ChromeWeb browser · Google
CVE-2010-3416
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 · uneditedGoogle Chrome before 6.0.472.59 on Linux does not properly implement the Khmer locale, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown 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 confidenceGoogle Chrome before 6.0.472.59 on Linux contains a flaw in the Khmer locale implementation that leads to memory corruption, allowing remote attackers to cause a denial of service or potentially achieve arbitrary code execution via unknown vectors.
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
ChromeWeb browser
< 6.0.472.59CVSS 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
- 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? 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Linux platformRun 'uname -a' or check OS identification to verify the system is Linux. This CVE only affects Google Chrome on Linux.Affected if The system is running Linux
-
Verify Google Chrome installationRun 'google-chrome --version' or 'chromium-browser --version' to check if Chrome/Chromium is installed.Affected if Google Chrome or Chromium is installed on the Linux system
-
Determine installed Chrome versionRun 'google-chrome --version' to obtain the exact version number of Google Chrome.Affected if The installed version is lower than 6.0.472.59
-
Check Khmer locale configurationInspect the system's locale settings using 'locale' command or check Chrome's language settings to see if Khmer locale is enabled.Affected if Khmer locale is actively used on the system
A user is affected if running Google Chrome on Linux with version lower than 6.0.472.59, especially when Khmer locale is configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.0.472.59
Upgrade Google Chrome to version 6.0.472.59 or later on affected Linux systems. For legacy environments where upgrade is not feasible, consider using an alternative browser or implementing application isolation.
Chrome 6.0.472.59 or later (note: Chrome versions from 2010 are obsolete; consider upgrading to the latest stable Chrome release for comprehensive security)
- 1. Check current Google Chrome version by navigating to chrome://settings/help or using 'About Google Chrome' in the menu
- 2. Download and install Google Chrome version 6.0.472.59 or later from the official Google Chrome website
- 3. Verify the installation was successful by checking the version again
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3416 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-3416 in production — separate from our analysis above.
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.
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.
- 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