Authentication bypass via hardcoded JWT signing secret
Published Mar 13, 2024 · Updated Aug 2, 2024
Authentication bypass in YourSpotify before 1.8.0 allows remote attackers to authenticate as arbitrary users through forged JWT cookies. The /spotify route signs tokens and the baselogged middleware verifies them with the same source-visible MyPrivateKey string in every deployment. Exploitation requires a valid userId, obtainable through the /accounts endpoint, and grants the target user's privileges, including administrator access.
Summary
What happened
Authentication bypass in YourSpotify before 1.8.0 allows remote attackers to authenticate as arbitrary users through forged JWT cookies. The /spotify route signs tokens and the baselogged middleware verifies them with the same source-visible MyPrivateKey string in every deployment. Exploitation requires a valid userId, obtainable through the /accounts endpoint, and grants the target user's privileges, including administrator access.
The record
- CVE
- CVE-2024-28194
- Published
- Mar 13, 2024
- Updated
- Aug 2, 2024
- Vendor
- Yooooomi
- Product
- YourSpotify
- Classifications
- CWE-798, CWE-321, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.8.0
- Affected versionversion=< 1.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA JWT forgery proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo