potpie through 2.0.0 Missing Ownership Check via code-changes sync
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| potpie-ai | potpie | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Potpie-ai | Potpie |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.389% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Potpie-ai
Potpie-ai potpie |
|
| Vendors & Products |
Potpie-ai
Potpie-ai potpie |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | potpie through 2.0.0 fails to verify user ownership on the POST /conversations/{conversation_id}/code-changes/sync endpoint. Authenticated attackers can write arbitrary file changes into other users' conversations by supplying their conversation IDs, allowing unauthorized modification of pending changes. | |
| Title | potpie through 2.0.0 Missing Ownership Check via code-changes sync | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|