| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/sylabs/singularity | ≤ 3.1.1all versions | |
| github.com/sylabs/singularity/v4 | < 4.4.2 | 4.4.2 |
The limit container paths directive in singularity.conf is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string, sibling directories with similar names may incorrectly be allowed.
For example, the configuration:
limit container paths = /data/safe
Will also allow containers in /data/safe-but-unsafe to be run.
This issue is patched in SingularityCE 4.4.2 and SingularityPRO 4.3.9 / 4.1.14
If you do not use the limit container paths functionality, then this issue does not affect your installation.
If you do use the limit container paths functionality then you must update. Please also review the documented limitations when user namespaces are enabled [1].
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free