dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2013-2133

MEDIUM · 5.5 CVSS v2.0 Published 2013-12-06
Fix available
A fix is available. Upgrade to after 6.1.0 or later.
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) before 6.2.0, does not properly enforce the method level restrictions for JAX-WS Service endpoints, which allows remote authenticated users to access otherwise restricted JAX-WS handlers by leveraging permissions to the EJB class.

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 Red Hat JBossWS fails to enforce method-level access restrictions for JAX-WS Service endpoints. Authenticated users with permissions to an EJB class can invoke restricted JAX-WS handlers that should be protected, due to improper access control enforcement in the EJB invocation handler implementation.

MitigationUpgrade to JBoss Enterprise Application Platform (EAP) 6.2.0 or later, which contains the fixed EJB invocation handler that properly enforces method-level restrictions for JAX-WS endpoints.

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.1.0= 4.2.0= 4.3.0= 5.0.0= 5.0.1= 5.1.0= 5.1.1= 5.1.2= 5.2.0= 5.2.1= 5.2.2= 6.0.0
Enterprise LinuxOperating system
Affected:= 5= 6.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 Enterprise Application Platform version
    Locate the JBoss/EAP installation and check the version file (typically in the root JBoss directory, often named 'version.txt' or accessible via the 'run.jar' manifest). Common locations include /opt/jboss-eap or similar installation paths.
    Affected if The installed version matches one of the affected versions: 4.2.0, 4.3.0, 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.1.2, 5.2.0, 5.2.1, 5.2.2, 6.0.0, or any version 6.1.0 or earlier.
  2. Determine if JAX-WS endpoints are deployed
    Search the deployment directory (typically 'deploy/' or ' deployments/') for JAX-WS descriptor files: web.xml containing <soap-address> or <service> elements, or wsdl files with SOAP binding. Also look for JAR files containing JAX-WS annotated classes (javax.jws.*).
    Affected if JAX-WS service endpoints are deployed on the JBoss server.
  3. Verify EJB-to-JAX-WS integration exists
    Examine deployed EJBs to identify those that expose JAX-WS web service interfaces. Look for EJB JARs with remote business interfaces that use javax.jws.WebService or javax.jws.WebMethod annotations, or check for EJB deployment descriptors (ejb-jar.xml) referencing service-endpoint-interface elements.
    Affected if EJBs are configured to expose web service endpoints (EJB3 webservices or JAX-WS service endpoints).
  4. Inspect method-level security constraints
    Review the deployment descriptors and annotations for JAX-WS endpoints to identify method-level access restrictions. Check for security-role-ref, security-role elements in ejb-jar.xml, or @RolesAllowed, @PermitAll, @DenyAll annotations on JAX-WS methods within EJB implementations.
    Affected if Method-level security constraints are defined but may not be properly enforced due to the vulnerability.
  5. Check for authenticated user access to EJB services
    Review the application's authentication configuration to determine if users authenticate to access the EJB/JAX-WS services. Examine login-config.xml, security-domain settings, or database-backed login modules.
    Affected if The application accepts authenticated users to invoke EJB-based JAX-WS services.

If the environment runs a JBoss/EAP version within the affected list, has deployed JAX-WS endpoints via EJBs, and relies on method-level access controls, the improper access control enforcement in the EJB invocation handler may allow authenticated users to bypass intended method restrictions.

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
Upgrade available Upgrade to a release after 6.1.0
Interim mitigation

Upgrade to JBoss Enterprise Application Platform (EAP) 6.2.0 or later, which contains the fixed EJB invocation handler that properly enforces method-level restrictions for JAX-WS endpoints.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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