Vulnerability in org.apache.ignite:ignite-core (CVE-2025-48977)
Summary
Vulnerability in org.apache.ignite:ignite-core (CVE-2025-48977). Confidential information can be exposed externally. Mitigation: upgrade to 2.18.0 or later.
Original description
The description as published by the source.
Relative Path Traversal vulnerability in Apache Ignite REST API.
Authenticated REST API users can read any file on the server with "cmd=log" command and a log path crafted in a certain way.
This issue affects Apache Ignite: from 2.0.0 through 2.17.0.
Users are recommended to upgrade to version 2.18.0, which fixes the issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2025-48977 has been found in org.apache.ignite:ignite-core.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade org.apache.ignite:ignite-core to 2.18.0 or later.
If unsure, ask your IT team or search "org.apache.ignite:ignite-core CVE-2025-48977" on the vendor's site.
CVE-2025-48977 (org.apache.ignite:ignite-core) — CWE-23 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.18.0 — 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-23) exists in org.apache.ignite:ignite-core.
Check the vendor advisory for the affected versions of org.apache.ignite:ignite-core.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 2.18.0.
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・依存マニフェストで org.apache.ignite:ignite-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.apache.ignite:ignite-core to 2.18.0ステージング環境で 2.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory openwall.com
- patch security@apache.org
- web nvd.nist.gov
- web github.com
- web github.com