dbcve.org
GeronimoApplication · Apache

CVE-2013-1777

HIGH · 10.0 CVSS v2.0 Published 2013-07-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The JMX Remoting functionality in Apache Geronimo 3.x before 3.0.1 (and IBM WAS Community Edition 3.0.0.3) improperly implements the RMI classloader, allowing remote attackers to send crafted serialized objects through the JMX connector and achieve arbitrary code execution.

MitigationUpgrade to Apache Geronimo 3.0.1 or later, or apply vendor patches; if upgrading is not feasible, disable JMX remoting or restrict network access to JMX ports.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GeronimoApplication
Affected:= 3.0
Websphere Application ServerApplication
Affected:= 3.0.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Geronimo or IBM WAS CE installation
    Look for the server installation directory - Geronimo is typically in 'geronimo' folder, IBM WAS CE in 'wasce' or 'WebSphereCE' folder. Check for 'bin/startup.sh', 'bin/geronimo.sh', or similar startup scripts.
    Affected if Either Apache Geronimo or IBM WAS Community Edition is installed on the system
  2. Determine the installed version
    Check version metadata: for Geronimo look in 'bin/geronimo-versioning.xml' or the manifest of startup scripts; for WAS CE check 'systeminfo' via the admin console or version files in the installation root.
    Affected if The version is exactly 3.0 for Apache Geronimo, or exactly 3.0.0.3 for IBM WAS Community Edition
  3. Verify JMX Remoting is enabled
    Examine the JMX connector configuration in 'var/config/username-password.properties' or 'etc/org.apache.geronimo.management.JMXSecurity.properties'. Also check 'deploy/plan/jmx-connector-plan.xml' if present. Look for RMI connector or JMX remoting configuration entries.
    Affected if JMX Remoting (RMI connector) is explicitly configured and enabled in the deployment plan or configuration files
  4. Confirm JMX ports are network-accessible
    Check network listening ports - JMX typically uses ports 9999 (Geronimo default) or 1099 (RMI registry). Review 'var/config/org.apache.geronimo.server.shell' or server startup logs for configured JMX ports. Use 'netstat -an' or 'ss -tlnp' to verify which ports are bound.
    Affected if JMX/RMI ports are bound to 0.0.0.0 or otherwise accessible from non-localhost interfaces

You are affected if you have Apache Geronimo 3.0 or IBM WAS Community Edition 3.0.0.3 installed with JMX Remoting enabled and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www-01.ibm.com →
Interim mitigation

Upgrade to Apache Geronimo 3.0.1 or later, or apply vendor patches; if upgrading is not feasible, disable JMX remoting or restrict network access to JMX ports.

Recommended fix High confidence

Apache Geronimo 3.0.1 or later

  1. Upgrade Apache Geronimo from version 3.0 to version 3.0.1 or later, as the vulnerability affects versions before 3.0.1
  2. For IBM WebSphere Application Server Community Edition 3.0.0.3, apply the IBM fix referenced in support document swg21643282
  3. If upgrading is not immediately possible, disable the JMX Remoting connector functionality or restrict network access to JMX ports
  4. Ensure JMX authentication is enabled and strong credentials are configured if JMX must remain enabled
Caveat Review release notes for 3.0.1 to check for any compatibility changes with deployed applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Geronimo Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1777 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data