Singularity Container Services Library vulnerabilitiesRanked by how likely they are to be used.
Singularity Container Services Library is made by Sylabs. We track 1 published vulnerability in it, across 4 versions. None of them is on the list of flaws known to be exploited today. If you run Singularity Container Services Library, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Singularity Container Services Library vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Singularity Container Services Library's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Singularity Container Services Library flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.7%CVE-2022-23538High
github.com/sylabs/scs-library-client is the Go client for the Singularity Container Services (SCS) Container Library Service.
Running Singularity Container Services Library? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Singularity Container Services Library on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1 published vulnerability listed under the name Singularity Container Services Library, across 4 versions.
None of Singularity Container Services Library's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Singularity Container Services Library. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.