How severe is CVE-2013-1777?

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

Which packages are affected by CVE-2013-1777?

CVE-2013-1777 affects the following packages: org.apache.geronimo.framework:geronimo-jmx-remoting (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-1777?

Update org.apache.geronimo.framework:geronimo-jmx-remoting to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1777 is resolved across your whole dependency graph.

How do I detect CVE-2013-1777 in my Maven dependencies?

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

How do I mitigate CVE-2013-1777 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-2013-1777 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-1777 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-2013-1777?

CVE-2013-1777 has an EPSS (Exploit Prediction Scoring System) score of 9.8%, placing it in the 96th 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-2013-1777?

CVE-2013-1777 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2013-1777 published, and has it been updated?

CVE-2013-1777 was published on May 17, 2022 and was last updated on December 3, 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-2013-1777 — geronimo-jmx-remoting

Fix: apache/geronimo@ee031c5

CVE-2013-1777 is a Code Injection vulnerability in org.apache.geronimo.framework:geronimo-jmx-remoting. A fix is available for org.apache.geronimo.framework:geronimo-jmx-remoting — see the affected versions and patch details below.

Apache Geronimo JMX Remoting functionality allows remote code execution in 3.x before v3.0.1

Published

May 17, 2022

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

9.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.geronimo.framework:geronimo-jmx-remoting

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 JMX Remoting functionality in Apache Geronimo 3.x before 3.0.1, as used in IBM WebSphere Application Server (WAS) Community Edition 3.0.0.3 and other products, does not properly implement the RMI classloader, which allows remote attackers to execute arbitrary code by using the JMX connector to send a crafted serialized object.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.geronimo.framework:geronimo-jmx-remoting`	≥ 3.0-beta-1&&< 3.0.1	3.0.1`org.apache.geronimo.framework:geronimo-jmx-remoting:3.0.1`

Affected Products

2 products · 4 configurations

Application

geronimoapache

1 version

3.0

Application

websphere application serveribm

1 version

3.0.0.3

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.geronimo.framework:geronimo-jmx-remoting, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.geronimo.framework:geronimo-jmx-remoting to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1777 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-1777 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works