CVE-2010-1766
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 · uneditedOff-by-one error in the WebSocketHandshake::readServerHandshake function in websockets/WebSocketHandshake.cpp in WebCore in WebKit before r56380, as used in Qt and other products, allows remote websockets servers to cause a denial of service (memory corruption) or possibly have unspecified other impact via an upgrade header that is long and invalid.
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 confidenceAn off-by-one error exists in WebCore's WebSocketHandshake::readServerHandshake function in WebKit. When a remote WebSocket server sends a specially crafted, overly long and invalid upgrade header, the function reads past buffer boundaries, causing memory corruption that leads to denial of service or potentially other unspecified impacts.
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<= 4.6.2<= r56379CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebKit library versionLocate the WebKit shared library (libwebkit or WebKit.dll) and check its version metadata using 'strings' or file properties, or query the application's linked librariesAffected if The WebKit version is r56379 or earlier (the revision number appears in library metadata or is reported by the application)
-
Identify Qt WebKit component versionFor Qt-based applications, check the Qt version and WebKit component version via 'qmake -query', the application's about dialog, or by inspecting QtCore/QtNetwork library filesAffected if Qt version is 4.6.2 or earlier, which includes the vulnerable WebKit component
-
Verify WebSocket support is enabledReview application configuration files, startup options, or runtime settings for WebSocket-enabled modules. Check if the application uses QtWebKit or direct WebSocket connectionsAffected if WebSocket functionality is actively enabled or the application serves WebSocket upgrade requests
-
Check for WebSocket handshake code in useMonitor network traffic or audit application logs for WebSocket upgrade attempts (look for 'Upgrade: websocket' headers in HTTP connections)Affected if The application acts as a WebSocket client or server and processes WebSocket handshake responses
A system is affected if it runs WebKit version r56379 or earlier, or Qt version 4.6.2 or earlier with WebKit, AND has WebSocket functionality enabled or processes WebSocket connections.
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.
From vendor dataUpdate WebKit to revision r56380 or later. For Qt-based applications, ensure Qt's WebKit component is patched to the fixed version.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1766 — 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-1766 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