Hard-coded System User Credentials in Folio Data Export Spring module

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2024-23685: 0.53% estimated exploitation activity in the next 30 days; percentile 44.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The module creates a system user that is used to perform internal module-to-module operations. Credentials for this user are hard-coded in the source code. This makes it trivial to authenticate as this user, allowing unauthorized read access to these mod-inventory-storage records: instances, holdings, items, contributor-types, identifier-types. This includes records marked as suppressed from discovery. Patches Upgrade mod-remote-storage to =2.0.3, or a 1.7.x version =1.7.1. Workarounds No known workarounds. References https://wiki.folio.org/x/hbMMBw - FOLIO Security Advisory with Upgrade Instructions https://github.com/folio-org/mod-remote-storage/commit/57df495f76e9aa5be9ce7ce3a65f89b6dbcbc13b - Fix

Published by the source

25 Jul 2023, 14:44 UTC

Last modified by the source

22 Jan 2026, 20:40 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m8v7-469p-5x89

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-23685

Advisory: Hard-coded System User Credentials in Folio Data Export Spring module
IDs: CVE-2024-23685, GHSA-m8v7-469p-5x89
Record: https://patchnext.com/advisories/cve-2024-23685 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.folio:mod-remote-storage 2.0.3, 1.7.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.folio:mod-remote-storage: affected >= 2.0.0, < 2.0.3; < 1.7.2; fixed in 2.0.3, 1.7.2

## Suggested inspection (read-only)
- Maven org.folio:mod-remote-storage: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.folio:mod-remote-storage.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m8v7-469p-5x89 (GitHub-reviewed advisory GHSA-m8v7-469p-5x89 lists affected ranges: Maven org.folio:mod-remote-storage >=2.0.0 =0 <1.7.2)

Commands are suggestions: review each one before running it.