CVE-2024-23329: changedetection.io API endpoint is not secured with API token

Published Jan 19, 2024
·
Updated

Summary

API endpoint /api/v1/watch/<uuid>/history can be accessed by any unauthorized user.

Details

WatchHistory resource does not have @auth.checktoken annotation, which means it can be accessed without providing x-api-key header.

https://github.com/dgtlmoon/changedetection.io/blob/9510345e01ea8e308c339163d8e8b030ce5ac7f1/changedetectionio/api/apiv1.py#L129-L156

PoC

1. Get list of watch with x-api-key: sh $ curl -H "x-api-key: apikeyhere" http://localhost:5000/api/v1/watch {"uuid": ...} 2. Call for history of snapshots without x-api-key. Expected - 401/403 error. Actual - list of snapshots is listed. sh $ 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.

Other sources

changedetection.io is an open source tool designed to monitor websites for content changes. In affected versions the API endpoint /api/v1/watch/<uuid>/history can be accessed by any unauthorized user. As a result any unauthorized user can check one's watch history. However, because unauthorized party first needs to know a 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. This issue has been addressed in version 0.45.13. Users are advised to upgrade. There are no known workarounds for this vulnerability.

MITRE

Affected Software

3 affected componentsFixes available
pip/changedetection.io>=0.39.14<=0.45.12
0.45.13
Changedetection Changedetection>=0.39.14<0.45.13
Webtechnologies Changedetection>=0.39.14<0.45.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/changedetection.io to a version that resolves this vulnerability.

    Fixed in 0.45.13
  2. Upgrade

    Upgrade changedetection.io to a version that resolves this vulnerability.

    Fixed in 0.45.13

Event History

Jan 19, 2024
CVE Published
via MITRE·07:49 PM
Data Sourced
via MITRE·07:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 23, 2024
Advisory Published
via GitHub·12:50 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-23329?

CVE-2024-23329 has been classified as a medium severity vulnerability due to unauthorized access to sensitive user data.

2

How do I fix CVE-2024-23329?

To fix CVE-2024-23329, update changedetection.io to version 0.45.13 or later.

3

What versions are affected by CVE-2024-23329?

CVE-2024-23329 affects versions of changedetection.io from 0.39.14 to 0.45.12 inclusive.

4

What specific data can be accessed through CVE-2024-23329?

CVE-2024-23329 allows unauthorized users to access the watch history of any user.

5

Is authentication required to exploit CVE-2024-23329?

No, CVE-2024-23329 can be exploited without any authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203