CVE-2024-23685: FOLIO mod-remote-storage Hard Coded Credentials
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.
Security readout for executives and security teams
Plain-English summary
This issue exposes some FOLIO inventory data because mod-remote-storage shipped with hard-coded credentials. An unauthenticated network user could read mod-inventory-storage records such as instances, holdings, items, contributor-types, and identifier-types. The known impact is data confidentiality only, not data modification or service disruption.
Executive priority
Treat as a moderate-priority confidentiality issue. Prioritize remediation for internet-reachable or broadly accessible FOLIO environments, because unauthorized users may read inventory metadata without credentials.
Technical view
CVE-2024-23685 is CWE-798 in org.folio:mod-remote-storage. Affected ranges are versions below 1.7.2 and 2.0.0 through 2.0.3. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is likely limited to organizations running FOLIO mod-remote-storage in the affected version ranges, especially where the service is reachable over a network by unauthenticated users.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The issue is still practical because exploitation requires no account and no user interaction, but the documented impact is read-only access to specific inventory records.
Researcher notes
Focus validation on version evidence and unauthenticated read exposure to mod-inventory-storage records. Do not assume broader FOLIO compromise, write access, or availability impact unless separate evidence supports it.
Mitigation direction
Upgrade mod-remote-storage to a version outside the affected ranges.
Review the GitHub advisory and patch commit for vendor remediation details.
Restrict network access to mod-remote-storage where operationally possible.
Rotate any credentials related to affected deployment paths if vendor guidance recommends it.
Validation and detection
Inventory deployed mod-remote-storage versions across FOLIO environments.
Confirm no instance runs below 1.7.2 or versions 2.0.0 through 2.0.3.
Review access logs for unauthenticated reads against inventory-storage-related records.
Verify patched deployments no longer contain the hard-coded credential behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-798 · source CWE mapping
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.