Improper Neutralization of Special Elements in Data Query Logic Affecting govulncheck-vulndb package, versions <0.0.20250207T224745-150000.1.32.1


Severity

Recommended
high

Based on SUSE Linux Enterprise Server security rating.

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Neutralization of Special Elements in Data Query Logic vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-SLES156-GOVULNCHECKVULNDB-8715777
  • published12 Feb 2025
  • disclosed11 Feb 2025

Introduced: 11 Feb 2025

NewCVE-2025-24787  (opens in a new tab)
CWE-943  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 govulncheck-vulndb to version 0.0.20250207T224745-150000.1.32.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream govulncheck-vulndb package and not the govulncheck-vulndb package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

WhoDB is an open source database management tool. In affected versions the application is vulnerable to parameter injection in database connection strings, which allows an attacker to read local files on the machine the application is running on. The application uses string concatenation to build database connection URIs which are then passed to corresponding libraries responsible for setting up the database connections. This string concatenation is done unsafely and without escaping or encoding the user input. This allows an user, in many cases, to inject arbitrary parameters into the URI string. These parameters can be potentially dangerous depending on the libraries used. One of these dangerous parameters is allowAllFiles in the library github.com/go-sql-driver/mysql. Should this be set to true, the library enables running the LOAD DATA LOCAL INFILE query on any file on the host machine (in this case, the machine that WhoDB is running on). By injecting &amp;allowAllFiles=true into the connection URI and connecting to any MySQL server (such as an attacker-controlled one), the attacker is able to read local files. 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.