{"answers":{"affected":"2 open source packages ship an affected version, including github.com/hpcng/singularity.","exploited":"There is no known exploitation of GHSA-jq42-hfch-42f3 in the wild and no public exploit code.","fix":"Upgrade github.com/hpcng/singularity to 3.7.4 or later.","what":"GHSA-jq42-hfch-42f3 is a vulnerability in github.com/hpcng/singularity, published on 1 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-jq42-hfch-42f3 and fix it if it is affected.\n\nWhat it is: GHSA-jq42-hfch-42f3 is a vulnerability in github.com/hpcng/singularity, published on 1 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-jq42-hfch-42f3 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/hpcng/singularity (Go): affected from 3.7.2; fixed in 3.7.4\n- github.com/hpcng/singularity (Go): affected from 3.7.2; fixed in 3.7.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-jq42-hfch-42f3/ (Markdown: https://insights.sbomify.com/GHSA-jq42-hfch-42f3/index.md)","id":"GHSA-jq42-hfch-42f3","markdown":"https://insights.sbomify.com/GHSA-jq42-hfch-42f3/index.md","name":"GHSA-jq42-hfch-42f3","record":{"aliases":[],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Singularity container runtime","requires_auth":"none","summary":"Attackers can execute malicious containers by exploiting a bug where Singularity ignores configured remote endpoints for library URIs, requiring user interaction to run the container.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"# Impact\nDue 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.\n\nAn 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.\n\nOnly action commands (`run`/`shell`/`exec`) against `library://` URIs are affected. Other commands such as `pull` / `push` respect the configured remote endpoint.\n\n# Patches\nAll users should upgrade to Singularity 3.7.4 or later.\n\n# Workarounds\nUsers who only interact with the default remote endpoint or do not use the library:// url are not affected.\n\nInstallations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected.\n\n# Acknowledgements\nThis issue was found by Mike Frisch and brought to our attention by Sylabs.  Sylabs is making a [coordinated disclosure](https://github.com/sylabs/singularity/security/advisories/GHSA-5mv9-q7fq-9394).\n\n# For more information\nGeneral questions about the impact of the advisory can be asked in the:\n\n[Singularity Slack Channel](https://join.slack.com/t/hpcng/shared_invite/zt-qda4h1ls-OP0Uouq6sSmVE6i_0NrWdw)\n[Singularity Mailing List](https://groups.google.com/a/lbl.gov/g/singularity)\nAny sensitive security concerns should be directed to: [singularity-security@hpcng.org](mailto:singularity-security@hpcng.org)","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint","id":"GHSA-jq42-hfch-42f3","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["3.7.4"],"introduced":["3.7.2"],"last_affected":[],"package":"github.com/hpcng/singularity","purl":null,"source":"GHSA-jq42-hfch-42f3"},{"ecosystem":"Go","fixed":["3.7.4"],"introduced":["3.7.2"],"last_affected":[],"package":"github.com/hpcng/singularity","purl":"pkg:golang/github.com/hpcng/singularity","source":"GHSA-jq42-hfch-42f3"}],"products":null,"published":"2021-06-01","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can execute malicious containers by exploiting a bug where Singularity ignores configured remote endpoints for library URIs, requiring user interaction to run the container.","url":"https://insights.sbomify.com/GHSA-jq42-hfch-42f3/"}