Singularity: Incorrect path matching for 'limit container paths' directive
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| sylabs | singularity | affected |
|
|||||||||
| sylabs | SingularityPRO | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sylabs | Singularity |
|
||||||||||||
| Sylabs | Singularitypro |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wqcr-7rf3-f64m | Singluarity: Incorrect path matching for 'limit container paths' directive |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.155% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sylabs
Sylabs singularity Sylabs singularitypro |
|
| Vendors & Products |
Sylabs
Sylabs singularity Sylabs singularitypro |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit container paths directive allows a container in a sibling directory such as /data/safe-but-unsafe to be run when /data/safe is allowed under setuid mode. This permits a user to run a container from outside the administrator's configured path allowlist. Installations that do not use limit container paths are not affected. This issue is fixed in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14. | |
| Title | Singularity: Incorrect path matching for 'limit container paths' directive | |
| Weaknesses | CWE-22 | |
| References |
|
|
| Metrics |
cvssV3_1
|