CVE-2024-56509

Improper input validation in the application can allow attackers to perform local file read (LFR) or path traversal attacks. These vulnerabilities occur when user input is used to construct file paths without adequate sanitization or validation. For example, using file:../../../etc/passwd or file: ///etc/passwd can bypass weak validations and allow unauthorized access to sensitive files. Even though this has been addressed in previous patch, it is still insufficient.

Details

The check in this line of code is insufficient.

if re.search(r'^file:/', url.strip(), re.IGNORECASE):

The attacker can still bypass this by using:
-file:../../../../etc/passwd
-file: ///etc/passwd (with space before /)

PoC

• Open up a changedetection.io instance with a webdriver configured.
• Create a new watch with file:../../../../etc/passwd.
• Check the watch preview.
• The contents of /etc/passwd should pop out.

Screenshots

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2024-56509 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.48.05); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-56509? CVE-2024-56509 is a high-severity path traversal vulnerability in changedetection.io (pip), affecting versions < 0.48.05. It is fixed in 0.48.05. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2024-56509? CVE-2024-56509 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of changedetection.io are affected by CVE-2024-56509? changedetection.io (pip) versions < 0.48.05 is affected.
4. Is there a fix for CVE-2024-56509? Yes. CVE-2024-56509 is fixed in 0.48.05. Upgrade to this version or later.
5. Is CVE-2024-56509 exploitable, and should I be worried? Whether CVE-2024-56509 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-56509 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-56509? Upgrade changedetection.io to 0.48.05 or later.