Vulnerability in org.folio:mod-remote-storage (CVE-2024-23685)
Summary
Vulnerability in org.folio:mod-remote-storage (CVE-2024-23685). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.2 or later.
Original description
The description as published by the source.
Hard-coded credentials in mod-remote-storage versions under 1.7.2 and from 2.0.0 to 2.0.3 allows unauthorized users to gain read access to mod-inventory-storage records including instances, holdings, items, contributor-types, and identifier-types.
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-23685 has been found in org.folio:mod-remote-storage.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade org.folio:mod-remote-storage to 1.7.2 or later.
If unsure, ask your IT team or search "org.folio:mod-remote-storage CVE-2024-23685" on the vendor's site.
CVE-2024-23685 (org.folio:mod-remote-storage) — CWE-798 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.7.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-798) exists in org.folio:mod-remote-storage.
Check the vendor advisory for the affected versions of org.folio:mod-remote-storage.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.7.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・依存マニフェストで org.folio:mod-remote-storage を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.folio:mod-remote-storage to 1.7.2ステージング環境で 1.7.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 repo.maven.apache.org