Skip to content

Navidrome Stores JWT Secret in Plaintext in navidrome.db

High severity GitHub Reviewed Published Dec 23, 2024 in navidrome/navidrome • Updated Dec 23, 2024

Package

gomod github.com/navidrome/navidrome (Go)

Affected versions

<= 0.53.3

Patched versions

0.54.1

Description

Navidrome stores the JWT secret in plaintext in the navidrome.db database file under the property table. This practice introduces a security risk because anyone with access to the database file can retrieve the secret.
The JWT secret is critical for the authentication and authorization system. If exposed, an attacker could:

  • Forge valid tokens to impersonate users, including administrative accounts.
  • Gain unauthorized access to sensitive data or perform privileged actions.
    This vulnerability has been tested on the latest version of Navidrome and poses a significant risk in environments where the database file is not adequately secured.

image

References

@deluan deluan published to navidrome/navidrome Dec 23, 2024
Published by the National Vulnerability Database Dec 23, 2024
Published to the GitHub Advisory Database Dec 23, 2024
Reviewed Dec 23, 2024
Last updated Dec 23, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-56362

GHSA ID

GHSA-xwx7-p63r-2rj8

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.