dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2014-3518

MEDIUM · 6.8 CVSS v2.0 Published 2014-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
jmx-remoting.sar in JBoss Remoting, as used in Red Hat JBoss Enterprise Application Platform (JEAP) 5.2.0, Red Hat JBoss BRMS 5.3.1, Red Hat JBoss Portal Platform 5.2.2, and Red Hat JBoss SOA Platform 5.3.1, does not properly implement the JSR 160 specification, which allows remote attackers to execute arbitrary code via unspecified vectors.

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 · moderate confidence

jmx-remoting.sar in JBoss Remoting fails to properly implement JSR 160 (Java Management Extensions JMX Remote API) specification, allowing remote attackers to execute arbitrary code by exploiting unspecified vectors in the JMX remoting implementation.

MitigationApply vendor-supplied patches or upgrade to newer versions of the affected JBoss products (JEAP 5.2.0, BRMS 5.3.1, Portal Platform 5.2.2, SOA Platform 5.3.1) that include the corrected JMX remoting implementation. Consider disabling JMX remoting if not required.

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
Jboss Enterprise Application PlatformApplication
Affected:= 5.2.0
Jboss Enterprise Brms PlatformApplication
Affected:= 5.3.1
Jboss Enterprise Portal PlatformApplication
Affected:= 5.2.2
Jboss Enterprise Soa PlatformApplication
Affected:= 5.3.1

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 JBoss product and version
    Check the installed JBoss version by looking at the version string in the installation directory, such as $JBOSS_HOME/readme.txt, or run: java -jar $JBOSS_HOME/bin/jboss-admin.jar --version (or check the startup logs)
    Affected if The installed version matches exactly 5.2.0 (JEAP), 5.3.1 (BRMS or SOA), or 5.2.2 (Portal Platform)
  2. Locate jmx-remoting.sar deployment
    Search for the jmx-remoting.sar file in the deployment directory, typically found in $JBOSS_HOME/server/<profile>/deploy/jmx-remoting.sar/ where <profile> is the active server profile (default, all, etc.)
    Affected if The jmx-remoting.sar directory or SAR archive exists in the deployed server profile
  3. Verify JMX remoting is exposed
    Check the jmx-remoting.sar/META-INF/jboss-service.xml configuration file for the JMX connector configuration. Look for entries with connector protocol settings and the bind address configuration. Also check if the JMXInvokerServlet is accessible at /invoker/JMXInvokerServlet
    Affected if JMX remoting connector is configured and bound to a network-accessible address (0.0.0.0 or non-localhost)
  4. Confirm JMX remote port is listening
    Run netstat -an or ss -tlnp on the JBoss host and look for the JMX remoting port (typically port 1090, 1098, 1099, or custom JMX connector port as configured in jboss-service.xml)
    Affected if The JMX remoting port is open and listening on an accessible network interface

You are affected if you run one of the specific JBoss versions (5.2.0, 5.3.1, or 5.2.2) AND have jmx-remoting.sar deployed with JMX remoting exposed on a reachable network interface.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or upgrade to newer versions of the affected JBoss products (JEAP 5.2.0, BRMS 5.3.1, Portal Platform 5.2.2, SOA Platform 5.3.1) that include the corrected JMX remoting implementation. Consider disabling JMX remoting if not required.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3518 — 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-2014-3518 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