| Package | Affected versions | Patched versions |
|---|---|---|
| changedetection-io | ≥ 0.39.14, < 0.45.13 | 0.45.13 |
| changedetection | ≥ 0.39.14, < 0.45.13 | 0.45.13 |
API endpoint /api/v1/watch/<uuid>/history can be accessed by any unauthorized user.
WatchHistory resource does not have @auth.check_token annotation, which means it can be accessed without providing x-api-key header.
x-api-key:$ curl -H "x-api-key: apikeyhere" http://localhost:5000/api/v1/watch
{"uuid": ...}
x-api-key. Expected - 401/403 error. Actual - list of snapshots is listed.$ curl http://localhost:5000/api/v1/watch/uuid/history
{"timestamp": "/path/to/snapshot.txt"}
Anybody can check one's watch history. However, because unauthorized party first needs to know watch UUID, and the watch history endpoint itself returns only paths to the snapshot on the server, an impact on users' data privacy is minimal.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free