dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2014-3464

MEDIUM · 5.5 CVSS v2.0 Published 2014-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable 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
The EJB invocation handler implementation in Red Hat JBossWS, as used in JBoss Enterprise Application Platform (EAP) 6.2.0 and 6.3.0, does not properly enforce the method level restrictions for outbound messages, which allows remote authenticated users to access otherwise restricted JAX-WS handlers by leveraging permissions to the EJB class. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-2133.

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 EJB invocation handler in JBossWS (JBoss EAP 6.2.0/6.3.0) fails to enforce method-level access restrictions on outbound JAX-WS messages. Authenticated users with permissions to an EJB class can bypass intended security boundaries and access restricted JAX-WS handlers. This is an incomplete fix for CVE-2013-2133.

MitigationApply the vendor patch for this vulnerability in JBoss EAP 6.2.0 and 6.3.0, which should properly enforce method-level restrictions for outbound messages in the EJB invocation handler.

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:= 6.2.0= 6.3.0

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

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

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 EAP version
    Check the installed JBoss EAP version by inspecting the version file in the JBoss home directory (typically $JBOSS_HOME/jboss-modules.jar or through the startup logs). You can also run: grep -r 'JBoss' $JBOSS_HOME/version.txt 2>/dev/null or check the runtime MBean via JMX console.
    Affected if The installed version is exactly 6.2.0 or exactly 6.3.0 (not patched)
  2. Confirm JAX-WS with EJB usage
    Inspect the deployment descriptors (ejb-jar.xml and web.xml) in your deployed EAR/WAR files, or check for JAX-WS annotated classes (such as @WebService, @WebMethod) in EJB beans within your application archives.
    Affected if The environment uses EJB beans that expose JAX-WS web service endpoints (JAX-WS handlers attached to EJB methods)
  3. Check for outbound JAX-WS message handlers
    Review the EJB implementation classes and their associated JAX-WS handler configuration files (handlers.xml or @HandlerChain annotations) to identify any method-level security constraints configured.
    Affected if The EJB has JAX-WS handlers configured but method-level access restrictions on outbound messages are not being enforced by the JBossWS EJB invocation handler
  4. Verify security constraint enforcement
    Test outbound JAX-WS message flow from the EJB to verify that method-level restrictions are properly applied. This requires reviewing the JBossWS EJB invocation handler configuration and testing with different authenticated user roles to confirm restrictions are enforced.
    Affected if An authenticated user with permissions to one EJB method can access restricted JAX-WS handlers on other EJB methods that should be protected (the access restriction is not enforced)

You are affected if running JBoss EAP 6.2.0 or 6.3.0 with EJB-based JAX-WS web services that have method-level security constraints which are not being properly enforced on outbound messages.

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 the vendor patch for this vulnerability in JBoss EAP 6.2.0 and 6.3.0, which should properly enforce method-level restrictions for outbound messages in the EJB invocation handler.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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