dbcve.org
WebkitWeb browser · Apple

CVE-2010-1386

HIGH · 10.0 CVSS v2.0 Published 2010-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
page/Geolocation.cpp in WebCore in WebKit before r56188 and before 1.2.5 does not properly restrict access to the lastPosition function, which has unspecified impact and remote attack vectors, aka rdar problem 7746357.

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

WebKit's WebCore Geolocation implementation in page/Geolocation.cpp fails to properly restrict access to the lastPosition function, allowing remote attackers to potentially retrieve geolocation data without proper user permission or authorization through unspecified attack vectors.

MitigationUpdate WebKit to revision r56188 or version 1.2.5 or later which contains the proper access controls for the lastPosition function. Review all geolocation permission requests in deployed applications to ensure they follow the corrected authorization model.

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
WebkitWeb browser
Affected:<= r56187= r50173

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. Identify WebKit geolocation usage
    Check if your application or product uses WebKit's Geolocation API by reviewing codebase for imports of Geolocation.h, navigator.geolocation, or references to WebCore/page/Geolocation.cpp
    Affected if The product uses WebKit with geolocation functionality enabled
  2. Determine WebKit revision
    Locate the WebKit source or compiled library and identify its revision number (typically found in source metadata, about dialog, or library version info)
    Affected if WebKit revision is r56187 or lower, or exactly r50173
  3. Verify lastPosition function accessibility
    Inspect the page/Geolocation.cpp source code or binary to confirm whether the lastPosition function lacks proper access control checks (look for missing permission validation before returning position data)
    Affected if The lastPosition function returns location data without requiring user authorization
  4. Check geolocation permission model
    Review how geolocation permission requests are implemented in the application - verify whether unauthorized scripts or frames can invoke the API without user prompts
    Affected if The geolocation API can be accessed without explicit user permission prompts

Your environment is affected if it uses WebKit with geolocation enabled and the WebKit revision is r56187 or lower, or exactly r50173, allowing unauthorized access to location data through the lastPosition function.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WebKit to revision r56188 or version 1.2.5 or later which contains the proper access controls for the lastPosition function. Review all geolocation permission requests in deployed applications to ensure they follow the corrected authorization model.

Recommended fix Moderate confidence

WebKit r56188 or later, or WebKit 1.2.5 or later

  1. Identify all applications and systems using the affected WebKit versions (r50173 through r56187)
  2. Obtain the fixed WebKit version (r56188 or later, or version 1.2.5 or later) from the official WebKit repository or your vendor
  3. Backup current configurations and data before performing the upgrade
  4. Replace the vulnerable WebKit library with the fixed version
  5. Restart all services or applications that depend on WebKit to load the updated library
  6. Verify the upgrade was successful by checking the WebKit revision or version number
  7. Test that Geolocation functionality works correctly after the update

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

Fix this in Webkit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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