OAuth token disclosure via permissive cache files
Published Feb 27, 2025 · Updated Feb 27, 2025
Incorrect default permissions in Spotipy before 2.25.1 allow local users to read cached Spotify OAuth tokens from shared systems. CacheFileHandler.save_token_to_cache writes token JSON using the process umask's default mode and does not restrict the resulting file from 0644 to 0600. Exploitation requires local access and a traversable cache path; the stolen token permits only the Spotify account actions granted by its scopes.
Summary
What happened
Incorrect default permissions in Spotipy before 2.25.1 allow local users to read cached Spotify OAuth tokens from shared systems. CacheFileHandler.save_token_to_cache writes token JSON using the process umask's default mode and does not restrict the resulting file from 0644 to 0600. Exploitation requires local access and a traversable cache path; the stolen token permits only the Spotify account actions granted by its scopes.
The record
- CVE
- CVE-2025-27154
- Published
- Feb 27, 2025
- Updated
- Feb 27, 2025
- Vendor
- Spotipy
- Product
- Spotipy
- Classifications
- CWE-276, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- Feb 27, 2025Record 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=< 2.25.1
What conditions does exploitation require?
What is affected?
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
- Upstream cache-permission 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