NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote EndpointGHSA-jq42-hfch-42f3

MEDIUM

GHSA-jq42-hfch-42f3 is a medium-severity (CVSS 6.3) vulnerability in github.com/hpcng/singularity. A fix is available for github.com/hpcng/singularity — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 5, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/hpcng/singularity

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 issue was found by Mike Frisch and brought to our attention by Sylabs. Sylabs is making a coordinated disclosure.

For more information

General questions about the impact of the advisory can be asked in the:

Singularity Slack Channel Singularity Mailing List Any sensitive security concerns should be directed to: [email protected]

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hpcng/singularity≥ 3.7.2&&< 3.7.43.7.4go get github.com/hpcng/singularity@v3.7.4

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hpcng/singularity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/hpcng/singularity to 3.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jq42-hfch-42f3 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

# 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. Othe
O3 Security · Impact-Aware SCA

Is GHSA-jq42-hfch-42f3 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Action Commands (run/shell/exec) Against Library URIs…