Vulnerability in org.folio:mod-data-export-spring (CVE-2024-23687)
Summary
Vulnerability in org.folio:mod-data-export-spring (CVE-2024-23687). Confidential information can be exposed externally. Mitigation: upgrade to 1.5.4 or later.
Original description
The description as published by the source.
Hard-coded credentials in FOLIO mod-data-export-spring versions before 1.5.4 and from 2.0.0 to 2.0.2 allows unauthenticated users to access critical APIs, modify user data, modify configurations including single-sign-on, and manipulate fees/fines.
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-2024-23687 has been found in org.folio:mod-data-export-spring.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade org.folio:mod-data-export-spring to 1.5.4 or later.
If unsure, ask your IT team or search "org.folio:mod-data-export-spring CVE-2024-23687" on the vendor's site.
CVE-2024-23687 (org.folio:mod-data-export-spring) — CWE-798 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.5.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-798) exists in org.folio:mod-data-export-spring.
Check the vendor advisory for the affected versions of org.folio:mod-data-export-spring.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 1.5.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・依存マニフェストで org.folio:mod-data-export-spring を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.folio:mod-data-export-spring to 1.5.4ステージング環境で 1.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web wiki.folio.org
- web github.com
- web repo.maven.apache.org