Most recent entries from all

EUVD-2026-368281

fkie_cve-2026-54447

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.

GHSA-wjhr-76vg-2hvc — garminconnect Has Insecure Permission Assignment for Garmin OAuth Token Store

Affected: PyPI: garminconnect

## Insecure Permission Assignment for Garmin OAuth Token Store

### Summary

`garminconnect` (≤ 0.3.4) wrote its OAuth token store to disk without restricting file-system permissions. Under the default Linux umask (`022`) the token file `garmin_tokens.json` was created world-readable (`0o644`). The file contains the DI **refresh token**, so any other local user on a shared host could read it and obtain persistent, unauthorized access to the victim's Garmin Connect account.

- **Severity:** High - **Weakness:** CWE-732 (Incorrect Permission Assignment for Critical Resource) - **Affected versions:** `<= 0.3.4` - **Patched version:** `0.3.5`

### Details

`Client.dump()` created the token directory and file with no `mode` argument, leaving permissions entirely to the process umask:

```python def dump(self, path: str) -> None: p = Path(path).expanduser() if p.is_dir() or not p.name.endswith(".json"): p = p / "garmin_tokens.json" p.parent.mkdir(parents=True, exist_ok=True) # no mode= p.write_text(self.dumps()) # no permission restriction ```

The serialized payload includes `di_token`, `di_refresh_token`, and `di_client_id`. The call is in the core library (`Garmin.login(tokenstore=...)` persists tokens this way), and all shipped usage examples default the token store to `~/.garminconnect`.

Under `umask 022` the resulting permissions were:

- token directory → `0o755` - `garmin_tokens.json` → `0o644` (world-readable)

A separate, un…

PYSEC-2026-3467 — garminconnect Has Insecure Permission Assignment for Garmin OAuth Token Store