Advisory

GHSA-x9xc-63hg-vcfq

Also known as: CVE-2024-27284, RUSTSEC-2024-0017

Summary

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

Details

Impact
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.

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

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-04-05 15:00 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

cassandra-cpp

crates.io · All systems

Affected

  • introduced 0, fixed 3.0.0 (semver)

Fixed versions

3.0.0

Fix

  • Fixed version 3.0.0
    cargo update -p cassandra-cpp --precise 3.0.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences