Skip to main content
No exploitation reportedFix available

CVE-2022-23538

No exploitation reported by the sources we read.

  • Published2023-01-17
  • Fixed in1.4.2 · 1.3.4
  • WeaknessCWE-522

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2023-01-1721:15CVE publishedNVD

Versions per branch

OSV · NVD
sylabs/scs-library-client
BranchAffectedFixed in
1.4≥ 1.4.0, < 1.4.21.4.2
1.3< 1.3.41.3.4
Sylabs singularity container services library
BranchAffectedFixed in
1.3= 1.3.2no fix published
1.3= 1.3.3no fix published
1.4= 1.4.0no fix published
1.4= 1.4.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • sylabs scs-library-client
    Affected
    • = < 1.34no fix stated
    • = >= 1.4.0, < 1.4.2no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-01-17

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apptaineropenSUSE:Tumbleweedall versions · fixed in 1.1.6-1.1
  • apptainerCleanStartall versions · fixed in 1.1.6-r0
  • apptainerAlpine:v3.24all versions · fixed in 1.1.6-r0
  • apptainerAlpine:v3.23all versions · fixed in 1.1.6-r0
  • apptainerAlpine:v3.22all versions · fixed in 1.1.6-r0
  • apptainerAlpine:v3.21all versions · fixed in 1.1.6-r0
  • apptainerAlpine:v3.20all versions · fixed in 1.1.6-r0
  • apptainerAlpine:v3.19all versions · fixed in 1.1.6-r0

5 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update sylabs/scs-library-client to 1.4.2 · 1.3.4

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-03-10
  • CNACVSS 3.15.2known since 2026-10-23
  • NVDCVSS 3.17.6read 2026-10-23
  • CNAweakness (CWE)CWE-522known since 2026-10-23
  • NVDweakness (CWE)CWE-522read 2026-10-23
  • FIRST EPSSEPSS score0.7 %2026-11-09
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2023-01-20

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
Published
2023-01-17
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-7p8m-22h4-9pj7

Frequently asked questions

What is CVE-2022-23538?

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.

Is CVE-2022-23538 actively exploited?

Active exploitation of CVE-2022-23538 has not been confirmed. Its EPSS score was 0.7% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-23538?

CVE-2022-23538 has a CVSS v3 base score of 7.6 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N.

Running sylabs/scs-library-client? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record