← Back
GHSA-f4gw-2p7v-4548
Vulnerability in axios (GHSA-f4gw-2p7v-4548)
Summary
vulnerability in axios (GHSA-f4gw-2p7v-4548). Risk of unauthorized operations or information disclosure. Exploitable via ``NO_PROXY``. Mitigation: upgrade to `0.33.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-f4gw-2p7v-4548** has been found in axios.
Attackers can target a specific entry point like ``NO_PROXY`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade axios to **0.33.0** or later.
If unsure, ask your IT team or search "axios GHSA-f4gw-2p7v-4548" on the vendor's site.
GHSA-f4gw-2p7v-4548 (axios) — CWE-183 /
Attack surface: `NO_PROXY` / `HTTP_PROXY` / `HTTPS_PROXY` / `localhost`
Patched: `0.33.0` — apply immediately
Workaround: set proxy: false
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-183) exists in axios. Attackers reach the vulnerable code path via ``NO_PROXY`` without authentication.
📍 Affected scope
axios — . Attack surface: `NO_PROXY` / `HTTP_PROXY` / `HTTPS_PROXY` / `localhost`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.33.0**.
🛡️ Workaround
Workaround: set proxy: false
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'axios' .` 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 'axios' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `axios` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
set proxy: falseパッチが適用されるまでの応急処置として、set proxy: false を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade axios to 0.33.0ステージング環境で 0.33.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
axios
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.33.0"}]}]
References
- web https://github.com/axios/axios/security/advisories/GHSA-f4gw-2p7v-4548
- web https://github.com/axios/axios/pull/11000
- web https://github.com/axios/axios/pull/11001
- web https://github.com/axios/axios/commit/1417285c69344bbcc6420a021f67dee0c6fedb2d
- web https://github.com/axios/axios/commit/32fc489632377d214db55bfa4e2c48486a7d7ce2
- web https://github.com/axios/axios/releases/tag/v0.33.0
- web https://github.com/axios/axios/releases/tag/v1.18.0
- web https://github.com/advisories/GHSA-f4gw-2p7v-4548