Approved changes feed: RSS · Atom
cpe:2.3:a:spotipy_project:spotipy:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Spotipy Project (1049ea1c-27f9-5ff2-88ed-42683f55b985) |
|---|---|
| Product | Spotipy (da79d666-748e-5341-82e4-cfb827142de2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/spotipy-dev/spotipy |
purl2cpe | 2026-06-01 10:17:50.277456 |
pkg:pypi/spotipy |
purl2cpe | 2026-06-01 10:17:50.277458 |
pkg:rpm/opensuse/python-spotipy |
purl2cpe | 2026-06-01 10:17:50.277459 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-27154 |
vulnerable | 2026-06-08 07:14:54.234112 |
Spotipy's cache file, containing spotify auth token, is created with overly broad permissions
Spotipy is a lightweight Python library for the Spotify Web API. The `CacheHandler` class creates a cache file to store the auth token. Prior to version 2.25.1, the file created has `rw-r--r--` (644) permissions by default, when it could be locked down to `rw-------` (600) permissions. This leads to overly broad exposure of the spotify auth token. If this token can be read by an attacker (another user on the machine, or a process running as another user), it can be used to perform administrative actions on the Spotify account, depending on the scope granted to the token. Version 2.25.1 tightens the cache file permissions.
Published: 2025-02-27T13:53:54.161Z
Updated: 2025-02-27T14:29:50.364Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-23608 |
vulnerable | 2026-06-08 05:56:03.763160 |
spotipy Path traversal vulnerability that may lead to type confusion in URI handling code
NONE
Spotipy is a light weight Python library for the Spotify Web API. In versions prior to 2.22.1, if a malicious URI is passed to the library, the library can be tricked into performing an operation on a different API endpoint than intended. The code Spotipy uses to parse URIs and URLs allows an attacker to insert arbitrary characters into the path that is used for API requests. Because it is possible to include "..", an attacker can redirect for example a track lookup via spotifyApi.track() to an arbitrary API endpoint like playlists, but this is possible for other endpoints as well. The impact of this vulnerability depends heavily on what operations a client application performs when it handles a URI from a user and how it uses the responses it receives from the API. This issue is patched in version 2.22.1.
Published: 2023-01-24T02:39:32.471Z
Updated: 2025-03-10T21:20:38.544Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.