CWE-1385: Missing Origin Validation in WebSockets

What is CWE-1385?

CWE-1385 is Missing Origin Validation in WebSockets. The flaw arises when The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid. The database currently holds 24 vulnerabilities mapped to CWE-1385 and none of them are in the CISA Known Exploited Vulnerabilities catalog.

OWASP Top 10 Rank-
Related CVES (365 days)24
AbstractionVariant
Likelihood of exploit-

Vulnerabilities mapped to CWE-1385

24 vulnerabilities167% increase year over year

No data

No vulnerability data in CISA KEV for CWE-1385

Official definition

ByMitre CWE

The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.

WebSockets provide a bi-directional low latency communication (near real-time) between a client and a server. WebSockets are different than HTTP in that the connections are long-lived, as the channel will remain open until the client or the server is ready to send the message, whereas in HTTP, once the response occurs (which typically happens immediately), the transaction completes.

A WebSocket can leverage the existing HTTP protocol over ports 80 and 443, but it is not limited to HTTP. WebSockets can make cross-origin requests that are not restricted by browser-based protection mechanisms such as the Same Origin Policy (SOP) or Cross-Origin Resource Sharing (CORS).

Characteristics

Alternate terms

  • Cross-Site WebSocket hijacking (CSWSH) — this term is used for attacks that exploit this weakness

Modes of introduction

  • Architecture and Design
  • Implementation

Common consequences

ImpactScopeExplanation
Varies by Context, Gain Privileges or Assume Identity, Bypass Protection Mechanism, Read Application Data, Modify Application Data, DoS: Crash, Exit, or RestartConfidentiality, Integrity, Availability, Non-Repudiation, Access ControlThis makes CSRF attacks more powerful. The consequences will vary depending on the nature of the functionality that is vulnerable to CSRF. An attacker could effectively perform any operations as the victim. If the victim is an administrator or privileged user, the consequences may include obtaining complete control over the web application - deleting or stealing data, uninstalling the product, or using it to launch other attacks against all of the product's users. Because the attacker has the identity of the victim, the scope of the CSRF is limited only by the victim's privileges.

Risk mitigations

  1. ImplementationEnable CORS-like access restrictions by verifying the 'Origin' header during the WebSocket handshake.
  2. ImplementationUse a randomized CSRF token to verify requests.
  3. ImplementationUse TLS to securely communicate using 'wss' (WebSocket Secure) instead of 'ws'.
  4. Architecture and Design, ImplementationRequire user authentication prior to the WebSocket connection being established. For example, the WS library in Node has a 'verifyClient' function.
  5. Implementation · Effectiveness: Defense in DepthLeverage rate limiting to prevent against DoS. Use of the leaky bucket algorithm can help with this.
  6. Implementation · Effectiveness: Defense in DepthUse a library that provides restriction of the payload size. For example, WS library for Node includes 'maxPayloadoption' that can be set.
  7. ImplementationTreat data/input as untrusted in both directions and apply the same data/input sanitization as XSS, SQLi, etc.

Representative vulnerabilities

Sources (2)

CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.

Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.