Summary
Navidrome has Multiple SQL Injections and ORM Leak
Security Advisory: Multiple Vulnerabilities in Navidrome
Navidrome automatically adds parameters in the URL to SQL queries. This can be exploited to access information by adding parameters like password=... in the URL (ORM Leak).
Furthermore, the names of the parameters are not properly escaped, leading to SQL Injections.
Finally, the username is used in a LIKE statement, allowing people to log in with % instead of their username.
Details
ORM Leak
When adding parameters to the URL, they are automatically included in an SQL LIKE statement (depending on the parameter's name). This allows attackers to potentially retrieve arbitrary information.
For example, attackers can use the following request to test whether some encrypted passwords start with AAA:
GET /api/user?_end=36&_order=DESC&password=AAA%
This results in an SQL query like password LIKE 'AAA%', allowing attackers to slowly brute-force passwords. (Also, any reason for using encryption instead of hashing?)
SQL Injections
When adding parameters to the URL, they are automatically added to an SQL query. The names of the parameters are not properly escaped.
This behavior can be used to inject arbitrary SQL code (SQL Injection), for example:
GET /api/album?_end=36&_order=DESC&_sort=recently_added&_start=0&SELECT+*+FROM+USER--=123 HTTP/1.1
This is only an example, but you should see an error message in the logs.
Authentication Weakness
When retrieving the user for authentication, the following code is used:
func (r *userRepository) FindByUsername(username string) (model.User, error) {
sel := r.newSelect().Columns("").Where(Like{"user_name": username})
var usr model.User
err := r.queryOne(sel, &usr)
return &usr, err
}
This relies on a LIKE statement and allows users to log in with % instead of the legitimate username.
Proof of Concept (PoC)
See above.
Credit
Louis Nyffenegger from PentesterLab
Impact
These vulnerabilities can be used to leak information and dump the contents of the database.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
CVE-2024-47062 has a CVSS score of 8.8 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.53.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-47062? CVE-2024-47062 is a critical-severity SQL injection vulnerability in github.com/navidrome/navidrome (go), affecting versions < 0.53.0. It is fixed in 0.53.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- How severe is CVE-2024-47062? CVE-2024-47062 has a CVSS score of 8.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/navidrome/navidrome are affected by CVE-2024-47062? github.com/navidrome/navidrome (go) versions < 0.53.0 is affected.
- Is there a fix for CVE-2024-47062? Yes. CVE-2024-47062 is fixed in 0.53.0. Upgrade to this version or later.
- Is CVE-2024-47062 exploitable, and should I be worried? Whether CVE-2024-47062 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-47062 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-47062? Upgrade
github.com/navidrome/navidrometo 0.53.0 or later.