How severe is GHSA-pmcr-2rhp-36hr?

No CVSS score has been assigned to GHSA-pmcr-2rhp-36hr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pmcr-2rhp-36hr?

GHSA-pmcr-2rhp-36hr affects the following packages: github.com/navidrome/navidrome (Go). Ecosystems affected: Go.

How do I fix GHSA-pmcr-2rhp-36hr?

Update github.com/navidrome/navidrome to 0.47.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pmcr-2rhp-36hr is resolved across your whole dependency graph.

How do I detect GHSA-pmcr-2rhp-36hr in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/navidrome/navidrome. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-pmcr-2rhp-36hr if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-pmcr-2rhp-36hr?

O3 pinpoints whether GHSA-pmcr-2rhp-36hr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-pmcr-2rhp-36hr actively exploited in the wild?

No public exploit code has been indexed for GHSA-pmcr-2rhp-36hr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-pmcr-2rhp-36hr?

GHSA-pmcr-2rhp-36hr is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-pmcr-2rhp-36hr published, and has it been updated?

GHSA-pmcr-2rhp-36hr was published on January 27, 2022 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-pmcr-2rhp-36hr

Fix: navidrome/navidrome@9e79b5c

GHSA-pmcr-2rhp-36hr is a SQL Injection vulnerability in github.com/navidrome/navidrome. O3 Security confirms whether GHSA-pmcr-2rhp-36hr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SQL injection in github.com/navidrome/navidrome

Also known asCVE-2022-23857GO-2022-0302

Published

Jan 27, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 21, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/navidrome/navidrome

Real-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

model/criteria/criteria.go in Navidrome before 0.47.5 is vulnerable to SQL injection attacks when processing crafted Smart Playlists. An authenticated user could abuse this to extract arbitrary data from the database, including the user table (which contains sensitive information such as the users' encrypted passwords).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/navidrome/navidrome`	all versions	0.47.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/navidrome/navidrome. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/navidrome/navidrome to 0.47.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pmcr-2rhp-36hr 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 pinpoints whether GHSA-pmcr-2rhp-36hr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-pmcr-2rhp-36hr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-pmcr-2rhp-36hr in your dependencies?

O3 detects GHSA-pmcr-2rhp-36hr across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works