devpi: Database contents leak
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| devpi | devpi | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Devpi | Devpi |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-m5pq-69xg-vcq3 | devpi-server may leak database contents |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.434% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Devpi
Devpi devpi |
|
| Vendors & Products |
Devpi
Devpi devpi |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | devpi is a Python package index staging server and packaging, testing, and release tool. Prior to 6.20.2 and 7.0.0b3, a server configured with the primary or deprecated master role allows an unauthenticated, modified GET request to the +changelog route because verify_primary does not reject a missing identity and therefore fails to require ReplicaIdentity. The response can disclose complete database content, including Argon2 password hashes and identifiers and salts for devpi-tokens; exposed hashes may be subject to dictionary attacks, and public tokens may assist attempts to derive the server secret. Large responses can also consume significant CPU, input/output capacity, and bandwidth. Servers using the standalone role are not exposed through replication, and an instance served exclusively through nginx with devpi-lockdown redirects the request to login with no known exploit. This issue is fixed in devpi-server versions 6.20.2 and 7.0.0b3. | |
| Title | devpi: Database contents leak | |
| Weaknesses | CWE-304 | |
| References |
| |
| Metrics |
cvssV3_1
|