Apptainer: 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 | ||||||
|---|---|---|---|---|---|---|---|---|---|
| apptainer | apptainer | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Apptainer | Apptainer |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cr2j-534f-mf3g | Apptainer has 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.150% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apptainer
Apptainer apptainer |
|
| Vendors & Products |
Apptainer
Apptainer apptainer |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Apptainer is an open source container platform. Prior to version 1.5.1, Image.AuthorizedPath applies plain string-prefix matching to the limit container paths directive in apptainer.conf, so an allowed path such as /data/safe also authorizes a sibling path such as /data/safe-but-unsafe. A local user can consequently run a container from a directory outside the administrator's intended allowlist when Apptainer operates in setuid mode. Installations that do not use setuid mode or do not configure limit container paths are not affected, and unrestricted user namespaces already allow users to run containers of their choice. This issue is fixed in version 1.5.1. | |
| Title | Apptainer: Incorrect path matching for 'limit container paths' directive | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|