ChromeWeb browser · Google
CVE-2010-2297
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 · uneditedrendering/FixedTableLayout.cpp in WebCore in WebKit in Google Chrome before 5.0.375.70 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via an HTML document that has a large colspan attribute within a table.
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 confidenceA vulnerability in WebCore's FixedTableLayout.cpp in WebKit allows remote attackers to cause a denial of service or potentially execute arbitrary code via an HTML document containing a table with an excessively large colspan attribute. The integer overflow or improper bounds checking when processing the colspan value leads to memory corruption.
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
< 5.0.375.70= 11.2= 11.3= 10= 11= 10= 11CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 Google Chrome versionOpen Chrome, go to Menu > Help > About Google Chrome, or navigate to chrome://version/ to see the full version numberAffected if The installed version is lower than 5.0.375.70
-
Check WebKit library version on SUSE/OpenSUSERun 'rpm -qa | grep -i webkit' or 'dpkg -l | grep -i webkit' to list installed WebKit packages, then check the version with 'rpm -qi <package-name>'Affected if WebKit library version is present from the affected SUSE/OpenSUSE versions (11.2, 11.3, or SLE 10/11)
-
Verify if using vulnerable WebKit applicationIdentify any installed applications that use WebKit (such as midori, epiphany, or other webkit-based browsers) and check their WebKit engine version using 'webkit-version' or checking the application's about/info dialogAffected if The application uses a WebKit engine version from before the colspan handling fix in FixedTableLayout.cpp
You are affected if you have Google Chrome before 5.0.375.70, or any WebKit-based application on SUSE/OpenSUSE 11.2, 11.3, or SLE 10/11 that has not been patched for the FixedTableLayout.cpp colspan integer overflow.
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 · scoped5.0.375.70
Update Google Chrome to version 5.0.375.70 or later, or update the WebKit library to a version containing the fix for FixedTableLayout.cpp colspan handling.
Google Chrome 5.0.375.70 or later (recommended: latest stable release)
- Open Google Chrome and navigate to the menu (three dots) in the top right corner
- Click on 'Help' and then select 'About Google Chrome'
- The browser will check for updates automatically
- If an update is available, click 'Update Google Chrome'
- Restart the browser to complete the installation of the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2297 — 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-2297 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