cassandra-cpp
Activity
- Latest release
- 2y ago
- Total releases
- 25
- Cadence
- ~2 months
- Last 12 months
- 0
Details
- License
- Apache-2.0
- First release
- Jun 29, 2017
| Version | Released | |
|---|---|---|
3.0.2
unknown
|
3.0.2
unknown
Dependencies (11)
+ 3 more |
|
3.0.1
unknown
|
3.0.1
unknown
Dependencies (11)
+ 3 more |
|
3.0.0
unknown
|
3.0.0
unknown
Dependencies (11)
+ 3 more |
|
2.0.1
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
2.0.1
unknown
Dependencies (10)
+ 2 more |
|
2.0.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
2.0.0
unknown
Dependencies (10)
+ 2 more |
|
1.2.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.2.0
unknown
Dependencies (10)
+ 2 more |
|
1.1.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.1.0
unknown
Dependencies (7)
|
|
1.0.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.0
unknown
Dependencies (7)
|
|
0.17.2
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.17.2
unknown
Dependencies (7)
|
|
0.17.1
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.17.1
unknown
Dependencies (8)
|
|
0.17.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.17.0
unknown
Dependencies (9)
+ 1 more |
|
0.16.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.16.0
unknown
Dependencies (9)
+ 1 more |
|
0.15.1
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.15.1
unknown
Dependencies (9)
+ 1 more |
|
0.15.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.15.0
unknown
Dependencies (9)
+ 1 more |
|
0.14.1
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.14.1
unknown
Dependencies (8)
|
|
0.14.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.14.0
unknown
Dependencies (8)
|
|
0.13.2
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.13.2
unknown
Dependencies (8)
|
|
0.13.1
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.13.1
unknown
Dependencies (8)
|
|
0.13.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.13.0
unknown
Dependencies (8)
|
|
0.12.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.12.0
unknown
Dependencies (8)
|
|
0.11.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.11.0
unknown
Dependencies (8)
|
|
0.10.2
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.10.2
unknown
Dependencies (12)
+ 4 more |
|
0.10.1
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.10.1
unknown
Dependencies (12)
+ 4 more |
|
0.10.0
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.10.0
unknown
Dependencies (13)
+ 5 more |
|
0.8.2
unknown
1 CVE
CVE-2024-27284
GHSA-x9xc-63hg-vcfq
RUSTSEC-2024-0017
Apr 05, 2024
cassandra-rs's non-idiomatic use of iterators leads to use after free
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactCode 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 PatchesThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern. WorkaroundsEnsure all usage fits the expected pattern. For example, use ReferencesNone. Fixed in
3.0.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.8.2
unknown
Dependencies (12)
+ 4 more |