How to fix: WebSocket connection uses unencrypted ws:// protocol
The page opens a WebSocket connection using the unencrypted ws:// protocol instead of the secure wss:// protocol.
Why it matters
An unencrypted WebSocket connection can be intercepted and read by any network observer or man-in-the-middle attacker, exposing all messages including authentication tokens, user data, and session information sent over the connection.
WebSocket connections should always use wss:// (WebSocket over TLS) in the same way that HTTP should be served over HTTPS.
How to fix it
- 1Change all ws:// WebSocket URLs to wss://
- 2Derive the protocol from the page protocol: location.protocol === "https:" ? "wss:" : "ws:"
- 3Configure your WebSocket server with a valid TLS certificate
Code examples
Use wss:// instead of ws://
// Unsafe: unencrypted WebSocket
const ws = new WebSocket('ws://example.com/socket');
// Safe: TLS-encrypted WebSocket
const ws = new WebSocket('wss://example.com/socket');References
Detected automatically by VulnRadar. The check id is websocket-unencrypted, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is WebSocket connection uses unencrypted ws:// protocol?
- VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id websocket-unencrypted, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does WebSocket connection uses unencrypted ws:// protocol map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.