Pi loads project-local extensions without approval
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| earendil-works | pi | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Earendil-works | Pi |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mqxh-6gq7-558m | Pi Agent: Pi loads project-local extensions without approval |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.165% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Earendil-works
Earendil-works pi |
|
| Vendors & Products |
Earendil-works
Earendil-works pi |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Pi is a minimal terminal coding harness. Pi before 0.79.0 loaded project-local configuration and resources from a repository's .pi directory without first asking the user to trust that repository. This included project-local extensions, which are executable TypeScript or JavaScript modules loaded into the Pi process. An attacker who controls a repository could place Pi-specific project resources in that repository. If a user then started Pi from that working tree, the project-local extension code could run with the same privileges as the local Pi process without the user having a convenient way to make a trust decision. This vulnerability is fixed in 0.79.0. | |
| Title | Pi loads project-local extensions without approval | |
| Weaknesses | CWE-829 | |
| References |
|
|
| Metrics |
cvssV3_1
|