Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 8.1 HIGHCVSS 2.0 · [email protected] · Primary 5.5 MEDIUMCVSS_V3 Publisher rating HIGHFixed by github.com/sylabs/singularity 3.6.3KEV status unknown

cve-program · CVE-2020-25039

Published

Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container execution.

Read the publisher's advisory

euvd · EUVD-2021-2599

Published

Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container execution.

Read the publisher's advisory

nvd · CVE-2020-25039

Published

Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container execution.

Read the publisher's advisory

osv · GHSA-w6v2-qchm-grj7

Published

### Impact Insecure permissions on temporary directories used in fakeroot or user namespace container execution. When a Singularity action command (run, shell, exec) is run with the fakeroot or user namespace option, Singularity will extract a container image to a temporary sandbox directory. Due to insecure permissions on the temporary directory it is possible for any user with access to the system to read the contents of the image. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running container. ### Patches This issue is addressed in Singularity 3.6.3. All users are advised to upgrade to 3.6.3. ### Workarounds The issue is mitigated if `TMPDIR` is set to a location that is only accessible to the user, as any subdirectories directly under `TMPDIR` cannot then be accessed by others. However, this is difficult to enforce so it is not recommended to rely on this as a mitigation. ### For more information General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the: * [Singularity Slack Channel](https://bit.ly/2m0g3lX) * [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity) Any sensitive security concerns should be directed to: [email protected] See our Security Policy here: https://sylabs.io/security-policy

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2020-25039

Published

n/a

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "n/a",
                    "vendor": "n/a",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "n/a"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2021-2599

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 16, 2020, 5:42:44 PM

dateUpdated: Aug 4, 2024, 3:26:09 PM

3 related source bulletins · separate from aliases

openSUSE-SU-2024:11384-1: singularity-3.8.3-1.2 on GA media

CVE-2018-12021 · CVE-2018-19295 · CVE-2019-11328 · CVE-2019-19724 · CVE-2020-13845 · CVE-2020-13846 · CVE-2020-13847 · CVE-2020-15229 · CVE-2020-25039 · CVE-2020-25040 · CVE-2021-29136 · CVE-2021-32635

openSUSE-SU-2020:1529-1: Security update for singularity

CVE-2020-25039 · CVE-2020-25040

openSUSE-SU-2020:1497-1: Security update for singularity

CVE-2020-25039 · CVE-2020-25040

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2020-25039

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-668

Original publisher date fields

published: 2020-09-16T18:15:13.467

lastModified: 2026-06-17T03:06:16.660

3 source CPE criteria · context only
  • cpe:2.3:a:sylabs:singularity:*:*:*:*:*:*:*:*
  • cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*
  • cpe:2.3:o:opensuse:leap:15.2:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-w6v2-qchm-grj7

Published

github.com/sylabs/singularity

Go

SEMVER · introduced 3.2.0 → fixed 3.6.3

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current