How severe is GHSA-6663-c963-2gqg?

No CVSS score has been assigned to GHSA-6663-c963-2gqg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6663-c963-2gqg?

GHSA-6663-c963-2gqg affects the following packages: ws (npm). Ecosystems affected: npm.

How do I fix GHSA-6663-c963-2gqg?

Update ws to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6663-c963-2gqg is resolved across your whole dependency graph.

How do I detect GHSA-6663-c963-2gqg in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ws. 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-6663-c963-2gqg 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-6663-c963-2gqg?

O3 pinpoints whether GHSA-6663-c963-2gqg 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-6663-c963-2gqg actively exploited in the wild?

No public exploit code has been indexed for GHSA-6663-c963-2gqg 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-6663-c963-2gqg?

GHSA-6663-c963-2gqg 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-6663-c963-2gqg published, and has it been updated?

GHSA-6663-c963-2gqg was published on February 18, 2019 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-6663-c963-2gqg

GHSA-6663-c963-2gqg is a Uncontrolled Resource Consumption vulnerability in ws. O3 Security confirms whether GHSA-6663-c963-2gqg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

DoS due to excessively large websocket message in ws

Also known asCVE-2016-10542

Published

Feb 18, 2019

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

📦ws

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 ws do not appropriately limit the size of incoming websocket payloads, which may result in a denial of service condition when the node process crashes after receiving a large payload.

Recommendation

Update to version 1.1.1 or later. Alternatively, set the maxpayload option for the ws server to a value smaller than 256MB.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ws`	all versions	1.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ws. 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 ws to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6663-c963-2gqg 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-6663-c963-2gqg 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-6663-c963-2gqg. 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 `ws` do not appropriately limit the size of incoming websocket payloads, which may result in a denial of service condition when the node process crashes after receiving a large payload. ## Recommendation Update to version 1.1.1 or later. Alternatively, set the `maxpayload` option for the `ws` server to a value smaller than 256MB.

O3 Security · Impact-Aware SCA

Is GHSA-6663-c963-2gqg in your dependencies?

O3 detects GHSA-6663-c963-2gqg 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