CVE-2019-11328
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 2.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.1% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 2.1% · EPSS, next 30 days
- Weakness
- CWE-732 · Incorrect permission assignment
- Record status
- Modified
Affected
- Sylabs Singularity < 3.2.0
- Sylabs Singularity 3.2.0
- Fedoraproject Fedora 28
- Fedoraproject Fedora 29
- Fedoraproject Fedora 30
- Opensuse Backports sle-15
- Opensuse Leap 15.1
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2019-11328.md and follow it. Check whether this project is affected by CVE-2019-11328. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/sylabs/singularity/releases/tag/v3.2.0
- https://github.com/sylabs/singularity/releases/tag/v3.2.0
References
- http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00028.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html
- http://www.openwall.com/lists/oss-security/2019/05/16/1
- http://www.securityfocus.com/bid/108360
- https://github.com/sylabs/singularity/releases/tag/v3.2.0
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5O3TPL5OOTIZEI4H6IQBCCISBARJ6WL3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LIHV7DSEVTB5SUPEZ2UXGS3Q6WMEQSO2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNU5BUHFOTYUZVHFUSX2VG4S3RCPUEMA/
- http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00028.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html
- http://www.openwall.com/lists/oss-security/2019/05/16/1
- http://www.securityfocus.com/bid/108360
- https://github.com/sylabs/singularity/releases/tag/v3.2.0
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5O3TPL5OOTIZEI4H6IQBCCISBARJ6WL3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LIHV7DSEVTB5SUPEZ2UXGS3Q6WMEQSO2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNU5BUHFOTYUZVHFUSX2VG4S3RCPUEMA/