ChromeWeb browser · Google
CVE-2010-1230
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 4.1.249.1036 does not have the expected behavior for attempts to delete Web SQL Databases and clear the Strict Transport Security (STS) state, which has unspecified impact and attack 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 versions before 4.1.249.1036 fail to properly handle Web SQL Database deletion requests and clearing of Strict Transport Security (STS) state, leading to unexpected behavior with unspecified security implications.
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
< 4.1.249.1036CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://settings/help or click Help > About Google Chrome to view the version numberAffected if Version is lower than 4.1.249.1036 (e.g., 4.1.249.x with a lower build number, or any 4.0.x or 3.x version)
-
Identify Web SQL Database usageReview web applications accessed in the browser for use of the window.webDatabase object or SQLDatabase API calls in JavaScript codeAffected if Web applications accessed use Web SQL Database functionality and the browser version is vulnerable
-
Identify STS state clearing scenariosInspect browser for any automation scripts, extensions, or test harnesses that programmatically clear STS/HSTS state via browser APIsAffected if Scripts or tools clear STS state and the browser version is vulnerable
User is affected if running Google Chrome version below 4.1.249.1036 AND using web applications that rely on Web SQL Database deletion or STS state clearing functionality
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 · scoped4.1.249.1036
Update Google Chrome to version 4.1.249.1036 or later to obtain the correct behavior for Web SQL Database deletion and STS state clearing.
Chrome 4.1.249.1036 or later (or latest stable Chrome release)
- Verify current Chrome version by navigating to chrome://settings/help or checking About Google Chrome in the menu
- Download and install Google Chrome 4.1.249.1036 or later from the official Chrome download page (google.com/chrome)
- Restart the browser after installation to complete the update
- Navigate to chrome://settings and verify that Web SQL Database deletion and STS state clearing now function correctly
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-1230 — 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-1230 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