dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2010-1815

MEDIUM · 6.8 CVSS v2.0 Published 2010-09-09
Fix available
A fix is available. Upgrade to 1.2.6 / 4.1 or later.
See remediation →
77/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
Use-after-free vulnerability in WebKit in Apple iOS before 4.1 on the iPhone and iPod touch, and webkitgtk before 1.2.6, allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving scrollbars.

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 confidence

Use-after-free vulnerability in WebKit's scrollbar handling allows remote attackers to execute arbitrary code or cause denial of service by accessing freed memory. The vulnerability affects webkitgtk before 1.2.6 and Apple iOS before 4.1 on iPhone and iPod touch.

MitigationUpdate webkitgtk to version 1.2.6 or later, and update iOS devices to version 4.1 or later. Alternatively, disable or restrict JavaScript execution in WebKit-based browsers as a temporary workaround.

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
Ubuntu LinuxOperating system
Affected:= 9.10= 10.04= 10.10
Iphone OsOperating system
Affected:< 4.1
WebkitgtkWeb browser
Affected:< 1.2.6

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 if a Linux system uses webkitgtk-based browsers
    Look for installed WebKit-based browsers such as Epiphany, Midori, or Arora using the package manager (dpkg -l or rpm -qa) or by checking the application list
    Affected if Any webkitgtk-based browser is installed on Ubuntu 9.10, 10.04, or 10.10
  2. Check webkitgtk library version on Linux
    Run 'dpkg -l libwebkit-1.0-0' on Debian/Ubuntu systems or query the installed package version using the system's package manager, then compare the version number to 1.2.6
    Affected if The installed webkitgtk library version is lower than 1.2.6
  3. Check iOS version on iPhone or iPod touch
    On the iOS device, go to Settings > General > About and note the Version number
    Affected if The iOS version is lower than 4.1
  4. Confirm the browser uses WebKit's default scrollbar rendering
    Verify that the installed browser uses WebKit for rendering (this is the default behavior for Epiphany, Midori, and other WebKit-based browsers on Linux)
    Affected if A WebKit-based browser is in use with default rendering settings (scrollbar handling is built into WebKit and cannot be disabled separately)

A system is affected if it runs webkitgtk versions below 1.2.6 on Ubuntu 9.10/10.04/10.10, or if it runs Apple iOS versions below 4.1 on iPhone or iPod touch devices.

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 1.2.6 / 4.1 or later
Fixed in 1.2.64.1
Interim mitigation

Update webkitgtk to version 1.2.6 or later, and update iOS devices to version 4.1 or later. Alternatively, disable or restrict JavaScript execution in WebKit-based browsers as a temporary workaround.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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