VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

cassandra-cpp: vulnerability history, versions and safety

cassandra-cpp is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 22 releases, from Feb 2024 to Apr 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cassandra-cpp vulnerabilities

Vulert verdict on cassandra-cpp 3.0.2 i

Updated on 23 Oct 2026

Good news: 3.0.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 67/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on 3.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.0.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 05 Apr 2024 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 144 i
  • Last release 28 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for cassandra-cpp, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.0.2 18 Jun 2024 none Apache-2.0 — Details →
3.0.1 29 Feb 2024 none Apache-2.0 — Details →
3.0.0 28 Feb 2024 none Apache-2.0 — Details →
2.0.1 08 Jun 2023 H1 U1 Apache-2.0 Yes Details →
2.0.0 13 Mar 2023 H1 U1 Apache-2.0 Yes Details →
1.2.0 14 Nov 2022 H1 U1 Apache-2.0 Yes Details →
1.1.0 31 Mar 2022 H1 U1 Apache-2.0 Yes Details →
1.0.0 30 Mar 2022 H1 U1 Apache-2.0 Yes Details →
0.17.2 09 Mar 2022 H1 U1 Apache-2.0 Yes Details →
0.17.1 24 Jan 2022 H1 U1 Apache-2.0 Yes Details →
0.17.0 17 May 2021 H1 U1 Apache-2.0 Yes Details →
0.16.0 10 Mar 2021 H1 U1 Apache-2.0 Yes Details →
0.15.1 02 Jun 2020 H1 U1 Apache-2.0 Yes Details →
0.15.0 28 Jan 2020 H1 U1 Apache-2.0 Yes Details →
0.14.1 12 Nov 2019 H1 U1 Apache-2.0 Yes Details →
0.14.0 22 Jan 2019 H1 U1 Apache-2.0 Yes Details →
0.13.2 15 Jan 2019 H1 U1 Apache-2.0 Yes Details →
0.13.1 08 Jan 2019 H1 U1 Apache-2.0 Yes Details →
0.13.0 04 Dec 2018 H1 U1 Apache-2.0 Yes Details →
0.12.0 04 Dec 2018 H1 U1 Apache-2.0 Yes Details →
0.11.0 26 Apr 2018 H1 U1 Apache-2.0 Yes Details →
0.10.2 11 Sep 2017 H1 U1 Apache-2.0 Yes Details →
0.10.1 30 Aug 2017 H1 U1 Apache-2.0 Yes Details →
0.10.0 03 Aug 2017 H1 U1 Apache-2.0 Yes Details →
0.8.2 29 Jun 2017 H1 U1 Apache-2.0 Yes Details →

All 25 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for cassandra-cpp

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2024-27284: cassandra-cpp - Non-idiomatic use of iterators leads to use after free 7.5 high 3.0.0 05 Apr 2024
Use-after-free vulnerability in cassandra-cpp N/A unrated 3.0.0 28 Feb 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About cassandra-cpp

Is cassandra-cpp safe to use?

Vulert records 2 vulnerabilities for cassandra-cpp in crates.io: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is cassandra-cpp's Vulert package health score?

Vulert scores cassandra-cpp 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of cassandra-cpp affected?

No. 3.0.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of cassandra-cpp should I use?

3.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does cassandra-cpp have?

2 vulnerabilities are recorded for cassandra-cpp in the crates.io ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new cassandra-cpp vulnerabilities disclosed?

0 vulnerabilities were recorded for cassandra-cpp in the last 12 months, and the oldest entry in this database dates to 28 Feb 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of cassandra-cpp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor cassandra-cpp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the cassandra-cpp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.