CVE-2024-27284

cassandra-rs's non-idiomatic use of iterators leads to use after free

Workarounds

Ensure all usage fits the expected pattern. For example, use get_first_row() rather than an iterator, or completely process an item before advancing the iterator with next().

References

None.

Code that attempts to use an item (e.g., a row) returned by an iterator after the iterator has advanced to the next item will be accessing freed memory and experience undefined behaviour. Code that uses the item and then advances the iterator is unaffected. This problem has always existed.

This is a use-after-free bug, so it's rated high severity. If your code uses a pre-3.0.0 version of cassandra-rs, and uses an item returned by a cassandra-rs iterator after calling next() on that iterator, then it is vulnerable. However, such code will almost always fail immediately - so we believe it is unlikely that any code using this pattern would have reached production. For peace of mind, we recommend you upgrade anyway.

Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.

CVE-2024-27284 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 (3.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern.

1. What is CVE-2024-27284? CVE-2024-27284 is a high-severity use after free vulnerability in cassandra-cpp (rust), affecting versions < 3.0.0. It is fixed in 3.0.0. Memory is accessed after it has been freed, leading to undefined behavior in native code.
2. How severe is CVE-2024-27284? CVE-2024-27284 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 cassandra-cpp are affected by CVE-2024-27284? cassandra-cpp (rust) versions < 3.0.0 is affected.
4. Is there a fix for CVE-2024-27284? Yes. CVE-2024-27284 is fixed in 3.0.0. Upgrade to this version or later.
5. Is CVE-2024-27284 exploitable, and should I be worried? Whether CVE-2024-27284 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-27284 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-27284? Upgrade cassandra-cpp to 3.0.0 or later.