CVE-2023-30601

Apache Cassandra: Privilege escalation when enabling FQL/Audit logs

Privilege escalation when enabling FQL/Audit logs allows user with JMX access to run arbitrary commands as the user running Apache Cassandra
This issue affects Apache Cassandra: from 4.0.0 through 4.0.9, from 4.1.0 through 4.1.1.

WORKAROUND
The vulnerability requires nodetool/JMX access to be exploitable, disable access for any non-trusted users.

MITIGATION
Upgrade to 4.0.10 or 4.1.2 and leave the new FQL/Auditlog configuration property allow_nodetool_archive_command as false.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2023-30601 has a CVSS score of 7.8 (High). The vector is requires local access, low 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 (4.1.2, 4.0.10); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2023-30601? CVE-2023-30601 is a high-severity improper privilege management vulnerability in org.apache.cassandra:cassandra-all (maven), affecting versions >= 4.1.0, < 4.1.2. It is fixed in 4.1.2, 4.0.10. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2023-30601? CVE-2023-30601 has a CVSS score of 7.8 (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 org.apache.cassandra:cassandra-all are affected by CVE-2023-30601? org.apache.cassandra:cassandra-all (maven) versions >= 4.1.0, < 4.1.2 is affected.
4. Is there a fix for CVE-2023-30601? Yes. CVE-2023-30601 is fixed in 4.1.2, 4.0.10. Upgrade to this version or later.
5. Is CVE-2023-30601 exploitable, and should I be worried? Whether CVE-2023-30601 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-2023-30601 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-2023-30601?
   • Upgrade org.apache.cassandra:cassandra-all to 4.1.2 or later
   • Upgrade org.apache.cassandra:cassandra-all to 4.0.10 or later

Other vulnerabilities in org.apache.cassandra:cassandra-all