How severe is CVE-2015-0225?

No CVSS score has been assigned to CVE-2015-0225 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-0225?

CVE-2015-0225 affects the following packages: org.apache.cassandra:apache-cassandra (Maven), org.apache.cassandra:apache-cassandra (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-0225?

Update org.apache.cassandra:apache-cassandra to 2.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0225 is resolved across your whole dependency graph.

How do I detect CVE-2015-0225 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cassandra:apache-cassandra, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-0225 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2015-0225 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-0225 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-0225?

CVE-2015-0225 has an EPSS (Exploit Prediction Scoring System) score of 6.6%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-0225?

CVE-2015-0225 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-0225 published, and has it been updated?

CVE-2015-0225 was published on May 14, 2022 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2015-0225 — apache-cassandra

CVE-2015-0225 is a CWE-77 vulnerability in org.apache.cassandra:apache-cassandra. A fix is available for org.apache.cassandra:apache-cassandra — see the affected versions and patch details below.

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

Published

May 14, 2022

Updated

Dec 5, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.cassandra:apache-cassandra☕org.apache.cassandra:apache-cassandra

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cassandra:apache-cassandra`	≥ 1.2.0&&< 2.0.14	2.0.14`org.apache.cassandra:apache-cassandra:2.0.14`
☕Maven	`org.apache.cassandra:apache-cassandra`	≥ 2.1.0&&< 2.1.4	2.1.4`org.apache.cassandra:apache-cassandra:2.1.4`

Affected Products

1 product · 38 configurations

Application

cassandraapache

38 versions

1.2.01.2.11.2.21.2.31.2.41.2.51.2.61.2.71.2.81.2.91.2.101.2.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cassandra:apache-cassandra, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cassandra:apache-cassandra to 2.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0225 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

RHSA-2015:1947Red Hat JBoss Operations Network 3.3

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-0225 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works