Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.5

Chrome can let attackers escape sandbox via WebSocket

CVE-2014-1703 · published 12 years ago
Summary

Google Chrome versions before 33.0.1750.149 have a flaw in its WebSocket handling that could let a remote attacker cause the browser to free memory incorrectly. This mistake may allow the attacker to break out of Chrome’s sandbox protection and potentially run code on the user’s computer. Update Chrome to a newer version or apply the vendor’s patch to fix the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
google chrome <= 33.0.1750.146
33.0.1750.0
33.0.1750.1
33.0.1750.2
33.0.1750.3
33.0.1750.4
33.0.1750.5
33.0.1750.6
33.0.1750.7
33.0.1750.8
33.0.1750.9
33.0.1750.10
95 more version ranges
cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
Original advisory text
Use-after-free vulnerability in the WebSocketDispatcherHost::SendOrDrop function in content/browser/renderer_host/websocket_dispatcher_host.cc in the Web Sockets implementation in Google Chrome bef...
Use-after-free vulnerability in the WebSocketDispatcherHost::SendOrDrop function in content/browser/renderer_host/websocket_dispatcher_host.cc in the Web Sockets implementation in Google Chrome before 33.0.1750.149 might allow remote attackers to bypass the sandbox protection mechanism by leveraging an incorrect deletion in a certain failure case.
References
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
7.5 High
Exploitation
1% chance of attack within 30 days
Type
CWE-399Resource Management Errors
Timeline
Published16 Mar 2014
Updated3 Nov 2026
First seen29 Sep 2026
Sources
CVE-2014-1703 · NVD
Track software like this
Free during beta