Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-m8v7-469p-5x89: Hard-coded System User Credentials in Folio Data Export Spring module

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

ghsa
#git#java#auth#maven

Package

maven org.folio:mod-remote-storage (Maven)

Affected versions

>= 2.0.0, < 2.0.3

< 1.7.2

Patched versions

2.0.3

1.7.2

Description

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
folio-org/mod-remote-storage@57df495 - Fix

References

  • GHSA-m8v7-469p-5x89
  • folio-org/mod-remote-storage@57df495
  • https://wiki.folio.org/x/hbMMBw

julianladisch published to folio-org/mod-remote-storage

Jul 24, 2023

Published to the GitHub Advisory Database

Jul 25, 2023

Reviewed

Jul 25, 2023

Last updated

Jul 25, 2023

ghsa: Latest News

GHSA-pj33-75x5-32j4: RabbitMQ HTTP API's queue deletion endpoint does not verify that the user has a required permission