Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Go github.com/hpcng/singularity >= 2.3.0, <= 2.5.1
Fixed in
2.5.2· Vendor fix available
Issue
Singularity 2.3.0 through 2.5.1 is affected by an incorrect access control on systems supporting overlay file system. When using the overlay option, a malicious user may access sensitive information by exploiting a few specific Singularity features.
Recommended action: Upgrade to 2.5.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Due to incorrect use of a default URL, singularity action commands (run/shell/exec) specifying a container using a library:// URI will always attempt to retrieve the container from the default remote endpoint (cloud.sylabs.io) rather than the configured remote endpoint. An attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container. Only action commands (run/shell/exec) against library:// URIs are affected. Other commands such as pull / push respect the configured remote endpoint. Patches All users should upgrade to Singularity 3.7.4 or later. Workarounds Users who only interact with the default remote endpoint or do not use the library:// url are not affected. Installations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected. Acknowledgements This…
Recommended action: Upgrade to 3.7.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.