Vulnerability in com.graphhopper:graphhopper-nav (CVE-2021-29506)
Summary
Vulnerability in com.graphhopper:graphhopper-nav (CVE-2021-29506). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.4 or later.
Original description
The description as published by the source.
GraphHopper is an open-source Java routing engine. In GrassHopper from version 2.0 and before version 2.4, there is a regular expression injection vulnerability that may lead to Denial of Service. This has been patched in 2.4 and 3.0 See this pull request for the fix: https://github.com/graphhopper/graphhopper/pull/2304
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-29506 has been found in com.graphhopper:graphhopper-nav.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.graphhopper:graphhopper-nav to 2.4 or later.
If unsure, ask your IT team or search "com.graphhopper:graphhopper-nav CVE-2021-29506" on the vendor's site.
CVE-2021-29506 (com.graphhopper:graphhopper-nav) — CWE-400
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.4 — 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-400) exists in com.graphhopper:graphhopper-nav.
Check the vendor advisory for the affected versions of com.graphhopper:graphhopper-nav.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.4.
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-nav を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.graphhopper:graphhopper-nav to 2.4ステージング環境で 2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com