Singularity Incorrect Access Control

published 2018-07-05 8y ago modified 2026-06-17 4mo ago also GHSA-4x32-h296-rg6j , EUVD-2022-2468

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits: 0; none known

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.

Patch / fix

fixed in 1 distros 2 links 1

go github.com/hpcng/singularity 2.5.2

ubuntu opensuse

singularity-container Ubuntu Pro 18.04 LTS 2.4.2-4ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2018-12021

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

singularity openSUSE Tumbleweed 3.8.3-1.2
singularity Package Hub 12 SP3 2.6.1-14.1
singularity Package Hub 12 SP3 2.3.2-11.1

opensuse advisories openSUSE-SU-2024:11384-1 openSUSE-SU-2019:0095-1 openSUSE-SU-2018:1969-1

github.com/singularityware/singularity/releases/tag/2.5.2 release

Is CVE-2018-12021 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.47% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	6.8	AV:N/AC:L/Au:S/C:C/I:N/A:N
GitHub	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/hpcng/singularity	>=2.3.0, <2.5.2	2.5.2

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

github.com /singularityware/singularity/releases/tag/2.5.2
web, release-notes, third-party-advisory
openwall.com /lists/oss-security/2019/05/16/1
mailing-list, web
nvd.nist.gov /vuln/detail/CVE-2018-12021
advisory
github.com /singularityware/singularity
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.