Skip to content
Fencer Intel
high 7.5

CVE-2015-0225 json

Improper Neutralization of Special Elements used in a Command in Apache Cassandra

published 11y ago modified 4mo ago also GHSA-w7f2-gjxf-2gm9 , EUVD-2022-5523

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.6%
EPSS 6.6% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

The default configuration in Apache Cassandra 1.2.0 through 1.2.19, 2.0.0 through 2.0.13, and 2.1.0 through 2.1.3 binds an unauthenticated JMX/RMI interface to all network interfaces, which allows remote attackers to execute arbitrary Java code via an RMI request.

Patch / fix

  • maven org.apache.cassandra:apache-cassandra 2.0.14, 2.1.4

Is CVE-2015-0225 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-0225 updated cvss 7.5

Cassandra: remote code execution via unauthenticated JMX/RMI interface

  • Red Hat JBoss Operations Network 3 cassandra
    affected: no fix available
  • Red Hat JBoss Operations Network 3.3
    fixed: vendor fix RHSA-2015:1947
  • Red Hat JBoss Operations Network 2 cassandra
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.65% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
maven org.apache.cassandra:apache-cassandra
>=1.2.0, <2.0.14
>=2.1.0, <2.1.4
2.0.14
2.1.4

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.