Summary
API endpoint /api/v1/watch/<uuid>/history
can be accessed by any unauthorized user.
Details
WatchHistory resource does not have @auth.check_token
annotation, which means it can be accessed without providing x-api-key
header.
https://github.com/dgtlmoon/changedetection.io/blob/9510345e01ea8e308c339163d8e8b030ce5ac7f1/changedetectionio/api/api_v1.py#L129-L156
PoC
- Get list of watch with
x-api-key
:
$ curl -H "x-api-key: apikeyhere" http://localhost:5000/api/v1/watch
{"uuid": ...}
- Call for history of snapshots without
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"}
Impact
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.
References
Summary
API endpoint
/api/v1/watch/<uuid>/history
can be accessed by any unauthorized user.Details
WatchHistory resource does not have
@auth.check_token
annotation, which means it can be accessed without providingx-api-key
header.https://github.com/dgtlmoon/changedetection.io/blob/9510345e01ea8e308c339163d8e8b030ce5ac7f1/changedetectionio/api/api_v1.py#L129-L156
PoC
x-api-key
:x-api-key
. Expected - 401/403 error. Actual - list of snapshots is listed.Impact
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.
References