First published: Tue May 14 2019(Updated: )
An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/sing/<user>/<instance>`. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Sylabs Singularity | >=3.1.0<3.2.0 | |
Sylabs Singularity | =3.2.0 | |
Sylabs Singularity | =3.2.0-rc1 | |
Sylabs Singularity | =3.2.0-rc2 | |
Fedoraproject Fedora | =28 | |
Fedoraproject Fedora | =29 | |
Fedoraproject Fedora | =30 | |
Opensuse Backports | =sle-15 | |
Opensuse Backports | =sle-15-sp1 | |
openSUSE Leap | =15.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2019-11328.
CVE-2019-11328 has a severity rating of 8.8 (Critical).
The affected software for CVE-2019-11328 includes Singularity versions 3.1.0 to 3.2.0-rc2, Sylabs Singularity, Fedora versions 28, 29, and 30, and openSUSE Leap 15.1.
A malicious user with local/network access to the host system can exploit CVE-2019-11328 by manipulating files within `/run/singularity/instances/sing/<user>/<instance>` due to insecure permissions.
To fix CVE-2019-11328, it is recommended to update to Singularity version 3.2.0 or later, which includes a fix for the vulnerability.