Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 3 May 2018 17:12:06 +0000
From: "Priedhorsky, Reid" <>
To: "" <>
Subject: Singularity's Linux kernel vulnerability claim


Singularity is a container runtime targeting the high-performance computing market. It appears to be the sole product of Sylabs, Inc. [1] and has both “community” (open source) and “pro” (closed source) versions.

Recently, the Singularity team announced on their blog [2], following up an earlier mailing list post [3], that they’ve found:

> an exploit vector to all container runtimes, that allows a malicious user to gain additional privileges within a container on hosts running kernels that do not support the PR_SET_NO_NEW_PRIVS feature

No technical details are publically available:

> Sylabs has not provided details about this exploit because there is no workaround short of upgrading the kernel or uninstalling Singularity. So giving more information will only help malicious parties.

We understand that details have been offered by Sylabs to at least one third party under NDA. This third party declined, but others may have accepted.

Sylabs does not plan to request a CVE (link in original):

> As of now, Sylabs will not request a  CVE for this issue because it only affects old kernels and CVE’s associated with PR_SET_NO_NEW_PRIVS have already been provided and resolved [4].

My questions:

1. Does anyone know what is going on with this alleged vulnerability?
2. Has anything been independently corroborated?
3. Would a CVE request be appropriate?



Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.