How severe is GHSA-hf5h-hh56-3vrg?

No CVSS score has been assigned to GHSA-hf5h-hh56-3vrg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hf5h-hh56-3vrg?

GHSA-hf5h-hh56-3vrg affects the following packages: uws (npm). Ecosystems affected: npm.

How do I fix GHSA-hf5h-hh56-3vrg?

Update uws to 0.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hf5h-hh56-3vrg is resolved across your whole dependency graph.

How do I detect GHSA-hf5h-hh56-3vrg in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uws. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hf5h-hh56-3vrg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hf5h-hh56-3vrg?

O3 pinpoints whether GHSA-hf5h-hh56-3vrg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hf5h-hh56-3vrg actively exploited in the wild?

No public exploit code has been indexed for GHSA-hf5h-hh56-3vrg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-hf5h-hh56-3vrg?

GHSA-hf5h-hh56-3vrg is classified as Uncontrolled Resource Consumption (CWE-400), Improper Input Validation (CWE-20). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hf5h-hh56-3vrg published, and has it been updated?

GHSA-hf5h-hh56-3vrg was published on September 1, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-hf5h-hh56-3vrg

Fix: uWebSockets/uWebSockets@37deefd

GHSA-hf5h-hh56-3vrg is a Uncontrolled Resource Consumption vulnerability in uws. O3 Security confirms whether GHSA-hf5h-hh56-3vrg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in uws

Also known asCVE-2016-10544

Published

Sep 1, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦uws

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Affected versions of uws do not properly handle large websocket messages when permessage-deflate is enabled, which may result in a denial of service condition.

If uws recieves a 256Mb websocket message when permessage-deflate is enabled, the server will compress the message prior to executing the length check, and subsequently extract the message prior to processing. This can result in a situation where an excessively large websocket message passes the length checks, yet still gets cast from a Buffer to a string, which will exceed v8's maximum string size and crash the process.

Recommendation

Update to version 0.10.9 or later.

Alternatively, disable permessage-deflate.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`uws`	≥ 0.10.0&&< 0.10.9	0.10.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uws. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update uws to 0.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hf5h-hh56-3vrg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hf5h-hh56-3vrg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hf5h-hh56-3vrg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `uws` do not properly handle large websocket messages when `permessage-deflate` is enabled, which may result in a denial of service condition. If `uws` recieves a 256Mb websocket message when `permessage-deflate` is enabled, the server will compress the message prior to executing the length check, and subsequently extract the message prior to processing. This can result in a situation where an excessively large websocket message passes the length checks, yet still gets cast from a Buffer to a string, which will exceed v8's maximum string size and crash the process. ## R

O3 Security · Impact-Aware SCA

Is GHSA-hf5h-hh56-3vrg in your dependencies?

O3 detects GHSA-hf5h-hh56-3vrg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works