https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 21:18:29 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-02456 bdu:2025-02456 https://cve.radiocsirt.org/vuln/bdu:2025-02456 https://cve.radiocsirt.org/vuln/euvd-2026-214084 EUVD-2026-214084 https://cve.radiocsirt.org/vuln/euvd-2026-214084 https://cve.radiocsirt.org/vuln/fkie_cve-2025-24786 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-24786 https://cve.radiocsirt.org/vuln/ghsa-9r4c-jwx3-3j76 <p><strong>Affected:</strong> Go: github.com/clidey/whodb/core</p> <p>### Summary</p> <p>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.</p> <p>### Details</p> <p>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</p> <p>If no databases are present in the default directory, the UI indicates that the user is unable to open any databases:</p> <p></p> <p>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. Source: https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L26</p> <p>No checks are performed whether the database file that is eventually opened actually resides in the default directory `/db`.</p> <p>This allows an attacker to use path traversal (`../../`) in order to open any Sqlite3 database present on the system.</p> <p>### PoC</p> <p>Before running the container, an example Sqlite3 database with dummy &#34;secret&#34; data was created: ```sh DB_FILE=$(mktemp) echo &#34;CREATE TABLE secret_t…</p> <p><strong>Affected:</strong> Go: github.com/clidey/whodb/core</p> <p>### Summary</p> <p>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.</p> <p>### Details</p> <p>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</p> <p>If no databases are present in the default directory, the UI indicates that the user is unable to open any databases:</p> <p></p> <p>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. Source: https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L26</p> <p>No checks are performed whether the database file that is eventually opened actually resides in the default directory `/db`.</p> <p>This allows an attacker to use path traversal (`../../`) in order to open any Sqlite3 database present on the system.</p> <p>### PoC</p> <p>Before running the container, an example Sqlite3 database with dummy &#34;secret&#34; data was created: ```sh DB_FILE=$(mktemp) echo &#34;CREATE TABLE secret_t…</p> https://cve.radiocsirt.org/vuln/ghsa-9r4c-jwx3-3j76 https://cve.radiocsirt.org/vuln/opensuse-su-2025:14754-1 <p>govulncheck-vulndb-0.0.20250207T224745-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250207T224745-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:14754-1 https://cve.radiocsirt.org/vuln/suse-su-2025:0429-1 <p>Security update for govulncheck-vulndb</p> <p>Security update for govulncheck-vulndb</p> https://cve.radiocsirt.org/vuln/suse-su-2025:0429-1