CyberRota Analysis
AI-GeneratedThe garminconnect Python API wrapper for Garmin Connect prior to version 0.3.5 is vulnerable due to improper file permissions that allow unprivileged users on shared Linux or macOS systems to access sensitive OAuth tokens stored in garmin_tokens.json. This exposure can lead to unauthorized access to a victim's Garmin Connect account, compromising personal health and activity data. Organizations using this software should prioritize updating to version 0.3.5 to mitigate the risk of credential theft and potential data breaches.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
garminconnect is a Python 3 API wrapper for Garmin Connect that retrieves statistics and manages activities. Prior to 0.3.5, garminconnect/client.py Client.dump creates the OAuth token directory and garmin_tokens.json without explicit owner-only modes, so a permissive umask such as 022 can leave the directory mode at 0755 and the token file mode at 0644. garmin_tokens.json contains di_refresh_token, and another unprivileged user on a shared Linux or macOS host can read the token and obtain persistent access to the victim's Garmin Connect account, including health, fitness, activity, and device data. The Garmin.login tokenstore path is affected, and a pre-existing loosely permissioned token file remains exposed until rewritten or manually restricted. This issue is fixed in version 0.3.5.