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.
The application combines the default directory `/db` with the database file name provided by the user using the `.Join()` function, but does not verify whether the resulting path actually points to a file in the `/db` directory. An attacker can pass a crafted value containing path traversal sequences (e.g., `../../`), which will cause it to exit the allowed directory and open any SQLite3 file accessible in the host file system. The vulnerability is exploitable without authentication — no access control blocks unauthorized use of this functionality.
An attacker can read any SQLite3 database located on the host, which may lead to the disclosure of sensitive data stored outside the intended application directory. Affected resources may include databases of other applications running on the same system.
WhoDB should be updated to version 0.45.0 or newer. The vendor states that no known workarounds for this vulnerability exist — the only recommendation is immediate update.
Clidey WhoDB — versions earlier than 0.45.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NClidey Whodb
APPClidey< 0.45.0