Medium

JBossWS JAX-WS Handler Method-Level Authorization Bypass

IdentifiersCVE-2013-2133CWE-862

CVE-2013-2133 is a missing-authorization flaw in the JBossWS EJB invocation handler implementation for JAX-WS Service endpoints. When a JAX-WS handler executes, method-level EJB role restrictions are not enforced; only class-level restrictions are applied. Consequently, authorization assigned to an EJB class can be incorrectly treated as sufficient to invoke handlers associated with otherwise restricted EJB methods. The issue affects JBoss Enterprise Application Platform before 6.2.0 and was also remediated in affected JBoss BPM Suite and JBoss BRMS releases.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An authenticated remote user with permission to access the affected EJB class can invoke JAX-WS handlers for which the user lacks the required method-level role. This bypasses intended authorization boundaries and can enable unauthorized operations with integrity impact. Confidentiality or availability impact is not established by the available information.

Mitigation

If you can’t patch tonight, do this now.

Until updates can be applied, restrict network access to JAX-WS endpoints, limit EJB class access to only fully trusted roles, and avoid relying on method-level EJB role restrictions as the sole control for sensitive JAX-WS handler operations. Implement compensating authorization checks at the service or handler layer and audit access to affected endpoints.

Remediation

Patch, then assume compromise.

Apply the vendor-provided security updates. Red Hat remediated the issue in JBoss Enterprise Application Platform 6.2 through RHSA-2013:1784 and in EAP 6 components for RHEL 5 through RHSA-2013:1785. JBoss BPM Suite 6.0 and JBoss BRMS 6.0 were remediated by upgrading to version 6.1.0. Products in Extended Life Support that do not receive a fix should be migrated to a supported, patched release.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Red HatEnterprise Linuxoperating_system

Red HatJboss Enterprise Application Platformapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

9 SOURCESView more in app

redhat accessNews

Jan 1, 2026

RHSA-2015:1009 - Security Advisory - Red Hat Customer Portal

JBoss WS flaw in which EJB3 role restrictions are not applied to JAX-WS handlers.

redhat accessNews

Jan 1, 2026

RHSA-2015:0851 - Security Advisory - Red Hat Customer Portal

A JBoss WS flaw in which EJB3 role restrictions are not applied to JAX-WS handlers.

redhat accessNews

Jan 1, 2026

RHSA-2015:0850 - Security Advisory - Red Hat Customer Portal

A JBoss Web Services authorization flaw in which EJB3 role restrictions are not enforced for JAX-WS handlers.

rhn redhatNews

Jan 1, 2026

RHSA-2015:0851 - Security Advisory - Red Hat Customer Portal

A JBoss Web Services flaw in which EJB3 role restrictions were not applied to JAX-WS handlers.

+5 more in the timeline

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity