Insecure configuration in DSPy lead to arbitrary file read when running untrusted code inside the sandbox
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Jfrog | Dspy | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-vvw2-h478-xwr3 | DSPy does not properly restrict file reads |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.338% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jfrog
Jfrog dspy |
|
| Vendors & Products |
Jfrog
Jfrog dspy |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The overly permissive sandbox configuration in DSPy allows attackers to steal sensitive files in cases when users build an AI agent which consumes user input and uses the “PythonInterpreter” class. | |
| Title | Insecure configuration in DSPy lead to arbitrary file read when running untrusted code inside the sandbox | |
| Weaknesses | CWE-653 | |
| References |
| |
| Metrics |
cvssV3_1
|