Security readout for executives and security teams
Plain-English summary
This flaw can let a remote WebSocket client crash a vulnerable Node.js service by sending compressed data that expands far beyond the server’s size check. The business impact is availability loss, not data theft, based on the supplied sources.
Executive priority
Treat this as a targeted availability risk. It deserves prompt remediation where affected WebSocket services are public-facing or business-critical, but the supplied evidence does not support data compromise or active exploitation.
Technical view
CVE-2016-10544 affects the uws Node module versions 0.10.0 through 0.10.8. With permessage-deflate enabled, a large message may compress below the 16 MB payload check, then inflate to about 256 MB and exceed V8’s maximum string size, crashing the Node process. CWE-400 applies.
Likely exposure
Exposure is likely limited to Node.js applications using the uws module in affected versions with permessage-deflate enabled on reachable WebSocket endpoints.
Exploitation context
The supplied sources describe a denial-of-service condition. They do not show known active exploitation, and the CVE is not listed as KEV in the provided bundle.
Researcher notes
Key validation hinges on dependency version and compression configuration. The source bundle identifies affected versions and failure mechanics, but does not provide CVSS scoring, exploit-in-the-wild evidence, or detailed remediation text beyond the advisory and fix reference.
Mitigation direction
- Inventory applications and dependencies for uws versions 0.10.0 through 0.10.8.
- Upgrade affected uws deployments following the vendor advisory or referenced fix commit.
- Prioritize internet-facing WebSocket services with permessage-deflate enabled.
- If upgrade is blocked, check vendor guidance before relying on configuration workarounds.
Validation and detection
- Review package manifests and lockfiles for affected uws versions.
- Confirm whether WebSocket endpoints enable permessage-deflate.
- Verify production builds no longer resolve uws 0.10.0 through 0.10.8.
- Check operational logs for unexplained Node process crashes during WebSocket traffic.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2016-10544 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/uWebSockets/uWebSockets/commit/37deefd01f0875e133ea967122e3a5e421b8fcd9CVE reference · x_refsource_MISC
- https://nodesecurity.io/advisories/149CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.