dbx: Unauthenticated arbitrary SQL execution in dbx-web (authentication fails open when no password is configured)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| t8y2 | dbx | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| T8y2 | Dbx |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.687% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
T8y2
T8y2 dbx |
|
| Vendors & Products |
T8y2
T8y2 dbx |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | dbx is a cross-platform database client for databases. Prior to 0.5.51, dbx-web auth_middleware in crates/dbx-web/src/auth.rs passes every protected request to the handler chain when password_hash is None. A fresh deployment reaches that state when DBX_PASSWORD is unset and no stored password exists, while crates/dbx-web/src/main.rs binds the service to 0.0.0.0 on port 4224 by default. An unauthenticated network attacker can call the /api/connection/connect and /api/query/execute routes to use configured database credentials and execute arbitrary SQL, allowing disclosure, modification, or destruction of data in connected databases. The desktop Tauri application is not affected because it binds only to loopback. This issue is fixed in version 0.5.51. | |
| Title | dbx: Unauthenticated arbitrary SQL execution in dbx-web (authentication fails open when no password is configured) | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV3_1
|