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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2022-23538)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Fedora 36 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2023-677d58bb20 advisory.

    Update to upstream 1.1.6

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 37 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2023-01ff262091 advisory.

    Update to upstream 1.1.6

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
245944	Linux Distros Unpatched Vulnerability : CVE-2022-23538	Nessus	Misc.	high
171782	Fedora 36 : apptainer (2023-677d58bb20)	Nessus	Fedora Local Security Checks	high
171773	Fedora 37 : apptainer (2023-01ff262091)	Nessus	Fedora Local Security Checks	high

Detections

Analytics

CVE-2022-23538

high

Tenable Plugins

high

high

high