← Back
GHSA-6vvh-pxr4-25r7
Vulnerability in web-token/jwt-experimental (GHSA-6vvh-pxr4-25r7)
Summary
vulnerability in web-token/jwt-experimental (GHSA-6vvh-pxr4-25r7). Risk of unauthorized operations or information disclosure. Exploitable via ``Chacha20Poly1305``. Mitigation: upgrade to `4.1.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-6vvh-pxr4-25r7** has been found in web-token/jwt-experimental.
Attackers can target a specific entry point like ``Chacha20Poly1305`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade web-token/jwt-experimental to **4.1.7** or later.
If unsure, ask your IT team or search "web-token/jwt-experimental GHSA-6vvh-pxr4-25r7" on the vendor's site.
GHSA-6vvh-pxr4-25r7 (web-token/jwt-experimental) — CWE-347 /
Attack surface: `Chacha20Poly1305` / `alg` / `tag`
Patched: `4.1.7` — apply immediately
Workaround: Do not use the experimental `Chacha20Poly1305` key-encryption algorithm for untrusted input until upgraded.
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.
❓ What is the problem
**A vulnerability** (CWE-347) exists in web-token/jwt-experimental. Attackers reach the vulnerable code path via ``Chacha20Poly1305`` without authentication.
📍 Affected scope
web-token/jwt-experimental — . Attack surface: `Chacha20Poly1305` / `alg` / `tag`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.1.7**.
🛡️ Workaround
Workaround: Do not use the experimental `Chacha20Poly1305` key-encryption algorithm for untrusted input until upgraded.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'web-token/jwt-experimental' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'web-token/jwt-experimental' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `web-token/jwt-experimental` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Do not use the experimental `Chacha20Poly1305` key-encryption algorithm for untrusted input until upgraded.パッチが適用されるまでの応急処置として、Do not use the experimental `Chacha20Poly1305` key-encryption algorithm for untrusted input until upgraded. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade web-token/jwt-experimental to 4.1.7ステージング環境で 4.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
web-token/jwt-experimental
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
composer
web-token/jwt-library
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.7"}]}]