Vulnerability in websocket-extensions (CVE-2020-7663)
Summary
Vulnerability in websocket-extensions (CVE-2020-7663). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.1.5 or later.
Original description
The description as published by the source.
Impact
The ReDoS flaw allows an attacker to exhaust the server's capacity to process incoming requests by sending a WebSocket handshake request containing a header of the following form:
Sec-WebSocket-Extensions: a; b="\c\c\c\c\c\c\c\c\c\c ...
That is, a header containing an unclosed string parameter value whose content is a repeating two-byte sequence of a backslash and some other character. The parser takes exponential time to reject this header as invalid, and this will block the processing of any other work on the same thread. Thus if you are running a single-threaded server, such a request can render your service completely unavailable.
Patches
Users should upgrade to version 0.1.5.
Workarounds
There are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating.
References
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-7663 has been found in websocket-extensions.
Risk of unauthorized operations or information disclosure.
What to do: upgrade websocket-extensions to 0.1.5 or later.
If unsure, ask your IT team or search "websocket-extensions CVE-2020-7663" on the vendor's site.
CVE-2020-7663 (websocket-extensions) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.1.5 — apply immediately
Workaround: There are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in websocket-extensions.
Check the vendor advisory for the affected versions of websocket-extensions.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.1.5.
Workaround: There are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'websocket-extensions' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'websocket-extensions' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
websocket-extensionsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating.パッチが適用されるまでの応急処置として、There are no known work-arounds other than disabling any public-facing WebSocket functionality you are operating. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade websocket-extensions to 0.1.5ステージング環境で 0.1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory usn.ubuntu.com
- advisory nvd.nist.gov
- package github.com
- web blog.jcoglan.com
- web github.com
- web lists.debian.org
- web github.com
- web snyk.io
- web github.com
- web usn.ubuntu.com