dbcve.org
WebkitWeb browser · Apple

CVE-2010-1760

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
loader/DocumentThreadableLoader.cpp in the XMLHttpRequest implementation in WebCore in WebKit before r58409 does not properly handle credentials during a cross-origin synchronous request, which has unspecified impact and remote attack vectors, aka rdar problem 7905150.

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 XMLHttpRequest implementation in DocumentThreadableLoader.cpp fails to properly handle credentials during cross-origin synchronous requests before revision r58409. This allows attackers to potentially access sensitive credentials or session data across origin boundaries due to improper credential handling in the synchronous XHR path.

MitigationUpgrade WebKit to revision r58409 or later, or migrate to a maintained WebKit fork that includes this security fix. Applications using WebKit-based components should ensure all dependencies are updated.

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:<= r58408= r50173= r56187= r56188= r56379

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-based application or browser
    Determine if the target application uses WebKit as its rendering engine. This includes Safari, iOS browsers, or any application embedding WebKit. Check product documentation or examine installed components for WebKit libraries (WebKit.dll, WebKit2.dll, libwebkit, etc.)
    Affected if The application is confirmed to use WebKit and the specific version cannot be verified as r58409 or later
  2. Check WebKit revision number
    For WebKit-based browsers like Safari, check the installed version. On macOS, use 'Safari > About Safari' or check /Applications/Safari.app/Contents/Info.plist for the build number. For embedded WebKit, examine the library version or build metadata. Compare the revision/build to the affected range: r58408 or earlier, or specifically r50173, r56187, r56188, r56379
    Affected if The WebKit revision is r58408 or lower, or exactly matches r50173, r56187, r56188, or r56379
  3. Verify synchronous XMLHttpRequest usage
    Audit application code or network traffic for synchronous XMLHttpRequest (XHR) calls. In JavaScript code, look for xhr.open(method, url, false) where the third parameter is false (synchronous). Check for any scripts or web content that invoke synchronous XHR requests
    Affected if The application or its web content uses synchronous XMLHttpRequest (xhr.open with async=false)
  4. Check for cross-origin requests with credentials
    Examine network traffic or code for cross-origin XHR requests that include credentials (withCredentials=true). Synchronous XHR to different origins with credentials enabled triggers the vulnerable code path in DocumentThreadableLoader.cpp
    Affected if Cross-origin synchronous XHR requests with credentials (withCredentials=true) are observed or present in the application code

A user is affected if their WebKit-based application or browser uses a revision at r58408 or earlier (or specifically r50173, r56187, r56188, r56379) AND processes synchronous XMLHttpRequest with credentials across different origins.

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

Upgrade WebKit to revision r58409 or later, or migrate to a maintained WebKit fork that includes this security fix. Applications using WebKit-based components should ensure all dependencies are updated.

Recommended fix High confidence

Any WebKit release or build containing revision r58409 or later

  1. Identify the current WebKit version in use by checking the build revision or version number
  2. Upgrade to a WebKit build that includes revision r58409 or later, which contains the fix for the improper credential handling in XMLHttpRequest cross-origin synchronous requests
  3. Verify the upgrade by checking that the build revision is > r58408
  4. Test that XMLHttpRequest functionality works correctly after the upgrade

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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