CVE-2013-1777: Apache Geronimo JMX Remoting Remote Code Execution

Summary

17/05/2022
Yes i
High
Not published

CVE-2013-1777: Apache Geronimo JMX Remoting functionality allows remote code execution in 3.x before v3.0.1. Affects org.apache.geronimo.framework:geronimo-jmx-remoting versions >= 3.0-beta-1, < 3.0.1. Fixed in 3.0.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Geronimo is an open-source Java EE application server that provides a runtime environment for Java applications. It includes various components and frameworks to support enterprise-level applications. One of these components is the Geronimo JMX Remoting functionality, which allows remote management and monitoring of Java applications through the Java Management Extensions (JMX) technology. This functionality is used in IBM WebSphere Application Server (WAS) Community Edition and other products. However, a vulnerability in the JMX Remoting functionality exposes these systems to remote code execution attacks.

Vulnerability Detail

The JMX Remoting functionality in Apache Geronimo 3.x before version 3.0.1 does not properly implement the RMI classloader. This flaw enables remote attackers to execute arbitrary code by exploiting the JMX connector to send a crafted serialized object. By leveraging this vulnerability, an attacker can execute malicious code on the target system, potentially leading to unauthorized access, data breaches, or further compromise of the affected application or server.

How To Fix

Minimum fixed version

3.0.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is strongly advised to apply the official fix by upgrading to Apache Geronimo version 3.0.1 or later.

Conclusion

The Apache Geronimo JMX Remoting functionality in versions before 3.0.1 is vulnerable to remote code execution. To mitigate this vulnerability, users should upgrade their Apache Geronimo installations to version 3.0.1 or later. It is crucial to promptly apply the fix to ensure the security of the systems. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.geronimo.framework:geronimo-jmx-remoting →

Share this vulnerability

FAQ

Apache Geronimo is an open-source Java EE application server that provides a runtime environment for Java applications. It includes various components and frameworks to support enterprise-level applications.

JMX Remoting is a functionality in Apache Geronimo that allows remote management and monitoring of Java applications through the Java Management Extensions (JMX) technology.

This vulnerability allows remote attackers to execute arbitrary code on systems running Apache Geronimo 3.x before version 3.0.1. This can lead to unauthorized access, data breaches, or further compromise of the affected application or server.

To fix this vulnerability, it is recommended to upgrade to Apache Geronimo version 3.0.1 or later.

There is no known workaround for this vulnerability. It is strongly advised to apply the official fix by upgrading to Apache Geronimo version 3.0.1 or later.

How To Fix

Minimum fixed version

3.0.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback