dbcve.org
ChromeWeb browser · Google

CVE-2010-2298

HIGH · 10.0 CVSS v2.0 Published 2010-06-15
Fix available
A fix is available. Upgrade to 5.0.375.70 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
browser/renderer_host/database_dispatcher_host.cc in Google Chrome before 5.0.375.70 on Linux does not properly handle ViewHostMsg_DatabaseOpenFile messages in chroot-based sandboxing, which allows remote attackers to bypass intended sandbox restrictions via vectors involving fchdir and chdir calls.

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

The database_dispatcher_host.cc in Google Chrome Linux (versions before 5.0.375.70) fails to properly validate ViewHostMsg_DatabaseOpenFile messages within the chroot-based sandbox environment. Attackers can exploit this by using fchdir and chdir system calls to escape the sandbox restrictions and gain unauthorized file system access.

MitigationUpgrade Google Chrome for Linux to version 5.0.375.70 or later to obtain the patched database_dispatcher_host.cc component.

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
Affected:< 5.0.375.70

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 Chrome version on Linux
    Open terminal and run: google-chrome --version or chrome --version or look in Help > About Google Chrome
    Affected if Version number displayed is lower than 5.0.375.70
  2. Confirm Chrome edition is Linux
    Run: google-chrome --version and verify the output includes Linux or check the installed package with dpkg -l | grep chrome or rpm -qa | grep chrome
    Affected if Running a Linux version of Chrome with version below 5.0.375.70
  3. Identify if sandbox is in use
    Check Chrome process: look for chrome-sandbox process or examine /proc/<pid>/status for sandbox-related attributes. Also check chrome://sandbox/ in browser
    Affected if The chroot-based sandbox is enabled and the Chrome version is below 5.0.375.70
  4. Determine database feature usage
    Inspect active web pages using database features: open chrome://inspect/#pages and check for pages using Web SQL/database, or review any open tabs with HTML5 database-driven applications
    Affected if The database feature (Web SQL) is actively being used while running a vulnerable Chrome version

You are affected if you are running Google Chrome for Linux with a version lower than 5.0.375.70 and using the chroot-based sandbox with database features enabled.

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

Upgrade Google Chrome for Linux to version 5.0.375.70 or later to obtain the patched database_dispatcher_host.cc component.

Recommended fix High confidence

Chrome 5.0.375.70 or later (preferably latest stable release)

  1. 1. Open Google Chrome and navigate to Help > About Google Chrome
  2. 2. Check the current version number displayed
  3. 3. If version is below 5.0.375.70, click 'Update Google Chrome' to install the latest version
  4. 4. Restart the browser after the update completes
  5. 5. Alternatively, download the latest stable Chrome from https://www.google.com/chrome/ and reinstall

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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