Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

cassandra-cpp

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5crates.ioPublished

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

    CVE-2024-27284 · GHSA-x9xc-63hg-vcfq

    Affected
    • crates.io cassandra-cpp < 3.0.0
    Fixed in
    3.0.0· Vendor fix available
    Issue
    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 getfirstrow() rather than an iterator, or completely process an…

    Recommended action: Upgrade to 3.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →