CVE-2024-47062 — navidrome
Fix: navidrome/navidrome@3107170CVE-2024-47062 is a SQL Injection vulnerability in github.com/navidrome/navidrome. A fix is available for github.com/navidrome/navidrome — see the affected versions and patch details below.
Multiple SQL Injections and ORM Leak in navidrome
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47062.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/navidrome/navidromeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Security Advisory: Multiple Vulnerabilities in Navidrome
Summary
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.
Impact
These vulnerabilities can be used to leak information and dump the contents of the database.
Credit
Louis Nyffenegger from PentesterLab
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/navidrome/navidrome | all versions | 0.53.0go get github.com/navidrome/navidrome@v0.53.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/navidrome/navidrome, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/navidrome/navidrome to 0.53.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47062 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-47062 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-47062. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2024-47062
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-47062 -u https://target- Template
- Navidrome < 0.53.0 - Authenticated SQL Injection
- Severity
- critical
- Impact
- Authenticated attackers can exploit SQL injection to extract sensitive database information including encrypted passwords.
- Remediation
- Update Navidrome to version 0.53.0 or later.
Template by ProjectDiscovery nuclei-templates (iamnoooob, rootxharsh, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-47062 in your dependencies?
O3 Security finds CVE-2024-47062 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.