CVE-2025-24786
published 2025-02-06CVE-2025-24786: WhoDB is an open source database management tool. While the application only displays Sqlite3 databases present in the directory `/db`, there is no path…
PriorityP265critical9.1CVSS 3.1
AVNACLPRNUINSUCHIHAN
EXPLOIT
EPSS
2.68%
83.9th percentile
WhoDB is an open source database management tool. While the application only displays Sqlite3 databases present in the directory `/db`, there is no path traversal prevention in place. This allows an unauthenticated attacker to open any Sqlite3 database present on the host machine that the application is running on. Affected versions of WhoDB allow users to connect to Sqlite3 databases. By default, the databases must be present in `/db/` (or alternatively `./tmp/` if development mode is enabled). If no databases are present in the default directory, the UI indicates that the user is unable to open any databases. The database file is an user-controlled value. This value is used in `.Join()` with the default directory, in order to get the full path of the database file to open. No checks are performed whether the database file that is eventually opened actually resides in the default directory `/db`. This allows an attacker to use path traversal (`../../`) in order to open any Sqlite3 database present on the system. This issue has been addressed in version 0.45.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected
26 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| clidey | whodb | < 0.45.0 | 0.45.0 |
| github.com | clidey_whodb_core | >= 0 < 0.0.0-20250127172032-547336ac73c8 | 0.0.0-20250127172032-547336ac73c8 |
| msrc | azl3_azcopy_10.22.1-1 | — | — |
| msrc | azl3_azcopy_10.24.0-1 | — | — |
| msrc | azl3_blobfuse2_2.1.0-4 | — | — |
| msrc | azl3_blobfuse2_2.3.0-1 | — | — |
| msrc | azl3_cert-manager_1.11.2-8 | — | — |
| msrc | azl3_cert-manager_1.12.12-1 | — | — |
| msrc | azl3_cf-cli_8.7.3-3 | — | — |
| msrc | azl3_cf-cli_8.7.3-6 | — | — |
| msrc | azl3_cloud-provider-kubevirt_0.5.1-1 | — | — |
| msrc | azl3_containerd_1.7.13-5 | — | — |
| msrc | azl3_containerd_1.7.13-8 | — | — |
| msrc | azl3_containerized-data-importer_1.57.0-14 | — | — |
| msrc | azl3_containerized-data-importer_1.57.0-6 | — | — |
| msrc | azl3_coredns_1.11.1-3 | — | — |
| msrc | azl3_coredns_1.11.1-4 | — | — |
| msrc | azl3_cri-tools_1.29.0-1 | — | — |
| msrc | azl3_cri-tools_1.30.1-1 | — | — |
| msrc | azl3_docker-buildx_0.12.1-1 | — | — |
| msrc | azl3_docker-buildx_0.14.0-1 | — | — |
| msrc | azl3_docker-cli_25.0.3-2 | — | — |
| msrc | azure_linux_3.0_arm | — | — |
| msrc | azure_linux_3.0_x64 | — | — |
| msrc | cbl_mariner_2.0_arm | — | — |
Detection & IOCsextracted from sources · hover to see the quote
command{"operationName":"Login","variables":{"credentials":{"Type":"Sqlite3","Hostname":"","Database":"../etc/secret.db","Username":"","Password":"","Advanced":[]}},"query":"mutation Login($credentials: LoginCredentials!) {\n Login(credentials: $credentials) {\n Status\n __typename\n }\n}"}↗
sigma↗
matchers: words: ['"Status":true', '"StatusResponse"'] condition: and; status: 200
- →Monitor POST requests to /api/query containing a 'Database' field with path traversal sequences (e.g., '../../') and Type 'Sqlite3', especially from unauthenticated sources. ↗
- →A successful exploit returns HTTP 200 with both '"Status":true' and '"StatusResponse"' in the response body to the /api/query Login mutation. ↗
- →The vulnerability is unauthenticated — no prior session or credentials are required to exploit the path traversal via the Login GraphQL mutation. ↗
- →FOFA fingerprinting query for exposed WhoDB instances: body="whodb" ↗
- →After successful exploitation, a session Token cookie is issued — monitor for Token cookie issuance following anomalous Login mutation requests with traversal paths. ↗
- ·The path traversal is only exploitable against Sqlite3 database files present on the host filesystem. The attacker cannot read arbitrary file types — only valid Sqlite3 databases can be opened. ↗
- ·Development mode changes the default database directory from /db/ to ./tmp/, which may affect path traversal depth calculations. ↗
- ·The vulnerability affects all WhoDB versions prior to 0.45.0; no workarounds exist — upgrade is the only remediation. ↗
CVSS provenance
nvdv3.19.1CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vendor_msrc7.5HIGH
vendor_oracle7.5HIGH
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
WhoDB has a path traversal opening Sqlite3 database in github.com/clidey/whodb/core
osv·2025-02-07
CVE-2025-24786 WhoDB has a path traversal opening Sqlite3 database in github.com/clidey/whodb/core
WhoDB has a path traversal opening Sqlite3 database in github.com/clidey/whodb/core
WhoDB has a path traversal opening Sqlite3 database in github.com/clidey/whodb/core
GHSA
WhoDB has a path traversal opening Sqlite3 database
ghsa·2025-02-06
CVE-2025-24786 [CRITICAL] CWE-22 WhoDB has a path traversal opening Sqlite3 database
WhoDB has a path traversal opening Sqlite3 database
### Summary
While the application only displays Sqlite3 databases present in the directory `/db`, there is no path traversal prevention in place. This allows an unauthenticated attacker to open any Sqlite3 database present on the host machine that the application is running on.
### Details
WhoDB allows users to connect to Sqlite3 databases. By default, the databases must be present in `/db/` (or alternatively `./tmp/` if development mode is enabled). Source: https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L14-L20
If no databases are present in the default directory, the UI indicates that the user is unable to open any databases:
The database file is an user-controlled val
OSV
WhoDB has a path traversal opening Sqlite3 database
osv·2025-02-06
CVE-2025-24786 [CRITICAL] WhoDB has a path traversal opening Sqlite3 database
WhoDB has a path traversal opening Sqlite3 database
### Summary
While the application only displays Sqlite3 databases present in the directory `/db`, there is no path traversal prevention in place. This allows an unauthenticated attacker to open any Sqlite3 database present on the host machine that the application is running on.
### Details
WhoDB allows users to connect to Sqlite3 databases. By default, the databases must be present in `/db/` (or alternatively `./tmp/` if development mode is enabled). Source: https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L14-L20
If no databases are present in the default directory, the UI indicates that the user is unable to open any databases:
The database file is an user-controlled val
Oracle
Oracle Oracle Communications Applications Risk Matrix: Core (Google Protobuf-Java) — CVE-2024-24786
vendor_oracle·2025-01-15·CVSS 7.5
CVE-2024-24786 [HIGH] Oracle Oracle Communications Applications Risk Matrix: Core (Google Protobuf-Java) — CVE-2024-24786
Oracle Oracle Communications Applications Risk Matrix: Core (Google Protobuf-Java) vulnerability
CVE: CVE-2024-24786
CVSS: 7.5
Protocol: HTTP
Remote exploit: Yes
Affected versions: Network
Advisory: cpujan2025 (JAN 2025)
Microsoft
Infinite loop in JSON unmarshaling in google.golang.org/protobuf
vendor_msrc·2024-03-12·CVSS 7.5
CVE-2024-24786 [HIGH] CWE-1286 Infinite loop in JSON unmarshaling in google.golang.org/protobuf
Infinite loop in JSON unmarshaling in google.golang.org/protobuf
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
Go: Go
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://le
No detection rules found.
Nuclei
WhoDB < 0.45.0 - Path Traversal
nuclei·CVSS 9.1
CVE-2025-24786 [CRITICAL] WhoDB < 0.45.0 - Path Traversal
WhoDB < 0.45.0 - Path Traversal
WhoDB contains a path traversal caused by lack of validation when opening database files, letting unauthenticated attackers access arbitrary Sqlite3 databases on the host system, exploit requires attacker to manipulate database filename input.
Template:
id: CVE-2025-24786
info:
name: WhoDB < 0.45.0 - Path Traversal
author: basicbeny
severity: high
description: |
WhoDB contains a path traversal caused by lack of validation when opening database files, letting unauthenticated attackers access arbitrary Sqlite3 databases on the host system, exploit requires attacker to manipulate database filename input.
impact: |
Attackers can access any Sqlite3 database on the system, potentially exposing sensitive data.
remediation: |
Upgrade to version 0.45.0 or later.
No writeups or analysis indexed.
https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L14-L20https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L26https://github.com/clidey/whodb/security/advisories/GHSA-9r4c-jwx3-3j76https://github.com/clidey/whodb/security/advisories/GHSA-9r4c-jwx3-3j76
2025-02-06
Published