CVE-2024-22050

Malicious URL drafting attack against iodines static file server may allow path traversal

Workarounds

A possible workaround would be to disable the static file service and it's X-Sendfile support, sending static files using nginx or a source code solution (sending the data dynamically).

However, it would be better to upgrade iodine to the latest version, as it also contains non-security related fixes.

For more information

If you have any questions or comments about this advisory:

• Email Boaz Segev

A path traversal vulnerability was detected in iodine's static file service. This vulnerability effects any application running iodine's static file server on an effected iodine version.

Malicious URL drafting may cause the static file server to attempt a response containing data from files that shouldn't be normally accessible from the public folder.

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-22050 has a CVSS score of 7.5 (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.7.34); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The vulnerability was patched in version 0.7.34. Please upgrade to the latest version.

1. What is CVE-2024-22050? CVE-2024-22050 is a high-severity path traversal vulnerability in iodine (rubygems), affecting versions < 0.7.34. It is fixed in 0.7.34. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2024-22050? CVE-2024-22050 has a CVSS score of 7.5 (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 iodine are affected by CVE-2024-22050? iodine (rubygems) versions < 0.7.34 is affected.
4. Is there a fix for CVE-2024-22050? Yes. CVE-2024-22050 is fixed in 0.7.34. Upgrade to this version or later.
5. Is CVE-2024-22050 exploitable, and should I be worried? Whether CVE-2024-22050 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-22050 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-22050? Upgrade iodine to 0.7.34 or later.

Other vulnerabilities in iodine