Copier safe template has arbitrary filesystem read access via symlinks when _preserve_symlinks: false
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| copier-org | copier | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Copier-org | Copier | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-xjhm-gp88-8pfx | Copier safe template has arbitrary filesystem read access via symlinks when _preserve_symlinks: false |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.239% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:copier-org:copier:*:*:*:*:*:python:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Copier-org
Copier-org copier |
|
| Vendors & Products |
Copier-org
Copier-org copier |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Copier is a library and CLI app for rendering project templates. Prior to version 9.11.2, Copier suggests that it's safe to generate a project from a safe template, i.e. one that doesn't use unsafe features like custom Jinja extensions which would require passing the `--UNSAFE,--trust` flag. As it turns out, a safe template can currently include arbitrary files/directories outside the local template clone location by using symlinks along with `_preserve_symlinks: false` (which is Copier's default setting). Version 9.11.2 patches the issue. | |
| Title | Copier safe template has arbitrary filesystem read access via symlinks when _preserve_symlinks: false | |
| Weaknesses | CWE-61 | |
| References |
| |
| Metrics |
cvssV4_0
|