Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2025-13465 medium CVSS 5.3

Vulnerability in lodash (CVE-2025-13465)

Summary

vulnerability in lodash (CVE-2025-13465). Risk of unauthorized operations or information disclosure. Exploitable via ``_.unset``. Mitigation: upgrade to `4.17.23` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2025-13465** has been found in lodash. Attackers can target a specific entry point like ``_.unset`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10. What to do: upgrade lodash to **4.17.23** or later. If unsure, ask your IT team or search "lodash CVE-2025-13465" on the vendor's site.
CVE-2025-13465 (lodash) — CWE-1321 / CVSS v3 5.3 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `_.unset` / `_.omit` Patched: `4.17.23` — apply immediately 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-1321) exists in lodash. Attackers reach the vulnerable code path via ``_.unset`` without authentication.
📍 Affected scope
lodash — . Attack surface: `_.unset` / `_.omit`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.17.23**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'lodash' .` 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

  1. 1
    Identify exposure identify 
    grep -r 'lodash' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `lodash` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade lodash to 4.17.23

    ステージング環境で 4.17.23 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm lodash
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.17.23"}]}]
npm lodash.unset
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"last_affected":"4.5.2"}]}]
npm lodash-es
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.17.23"}]}]
npm lodash-amd
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.17.23"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →