Categories
CVE-2021-32635

Vulnerability in github.com/sylabs/singularity (CVE-2021-32635)

Summary

Vulnerability in github.com/sylabs/singularity (CVE-2021-32635). Risk of unauthorized operations or information disclosure. Exploitable via singularity. Mitigation: upgrade to 3.7.4 or later.

Original description

The description as published by the source.

Singularity is an open source container platform. In verions 3.7.2 and 3.7.3, Dde 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. The vulnerability is patched in Singularity version 3.7.4. Two possible workarounds exist: Users can only interact with the default remote endpoint, or an installation can have an execution control list configured to restrict execution to containers signed with specific secure keys.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-32635 has been found in github.com/sylabs/singularity.
Attackers can target a specific entry point like singularity over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/sylabs/singularity to 3.7.4 or later.
If unsure, ask your IT team or search "github.com/sylabs/singularity CVE-2021-32635" on the vendor's site.

CVE-2021-32635 (github.com/sylabs/singularity) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: singularity / run / shell / exec
Patched: 3.7.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in github.com/sylabs/singularity. Attackers reach the vulnerable code path via singularity without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/sylabs/singularity. Attack surface: singularity / run / shell / exec.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.7.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/sylabs/singularity' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/sylabs/singularity' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/sylabs/singularity を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/sylabs/singularity to 3.7.4

    ステージング環境で 3.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/sylabs/singularity
[{"type":"SEMVER","events":[{"introduced":"3.7.2"},{"fixed":"3.7.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details