Vulnerability in com.graphhopper:graphhopper-web-bundle (CVE-2021-23408)
Summary
Vulnerability in com.graphhopper:graphhopper-web-bundle (CVE-2021-23408). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.2 or later.
Original description
The description as published by the source.
This affects the package com.graphhopper:graphhopper-web-bundle before 3.2, from 4.0-pre1 and before 4.0. The URL parser could be tricked into adding or modifying properties of Object.prototype using a constructor or proto payload.
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-2021-23408 has been found in com.graphhopper:graphhopper-web-bundle.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.graphhopper:graphhopper-web-bundle to 3.2 or later.
If unsure, ask your IT team or search "com.graphhopper:graphhopper-web-bundle CVE-2021-23408" on the vendor's site.
CVE-2021-23408 (com.graphhopper:graphhopper-web-bundle) — CWE-1321
Attack vector: remote (network-reachable) / unauthenticated
Patched: 3.2 — 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.
A vulnerability (CWE-1321) exists in com.graphhopper:graphhopper-web-bundle.
Check the vendor advisory for the affected versions of com.graphhopper:graphhopper-web-bundle.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.graphhopper:graphhopper-web-bundle を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.graphhopper:graphhopper-web-bundle to 3.2ステージング環境で 3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- patch github.com
- report snyk.io