CVE-2011-1483 — jbossws-common
CVE-2011-1483 is a security vulnerability in org.jboss.ws:jbossws-common. A fix is available for org.jboss.ws:jbossws-common — see the affected versions and patch details below.
JBossWS vulnerable to uncontrolled recursion
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.jboss.ws:jbossws-commonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
wsf/common/DOMUtils.java in JBossWS Native in Red Hat JBoss Enterprise Application Platform 4.2.0.CP09, 4.3, and 5.1.1; JBoss Enterprise Portal Platform 4.3.CP06 and 5.1.1; JBoss Enterprise SOA Platform 4.2.CP05, 4.3.CP05, and 5.1.0; JBoss Communications Platform 1.2.11 and 5.1.1; JBoss Enterprise BRMS Platform 5.1.0; and JBoss Enterprise Web Platform 5.1.1 does not properly handle recursion during entity expansion, which allows remote attackers to cause a denial of service (memory and CPU consumption) via a crafted request containing an XML document with a DOCTYPE declaration and a large number of nested entity references, a similar issue to CVE-2003-1564.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jboss.ws:jbossws-common | all versions | 2.1.0.Finalorg.jboss.ws:jbossws-common:2.1.0.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.ws:jbossws-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.ws:jbossws-common to 2.1.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-1483 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-1483 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2011-1483. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| JBEAP 4.2.0 for RHEL 5 | jbossas-0:4.2.0-6.GA_CP09.11.1.ep1.el5 | RHSA-2011:1309 |
| JBEWP 5 for RHEL 5 | jbossws-common-0:1.1.0-4.SP7_patch_02.1.ep5.el5 | RHSA-2011:1303 |
| JBoss Communications Platform 1.2 | see advisory | RHSA-2011:1308 |
| JBoss Enterprise BRMS Platform 5.1 | see advisory | RHSA-2011:1313 |
| Red Hat JBoss Enterprise Application Platform 4.2 | see advisory | RHSA-2011:1310 |
| Red Hat JBoss Enterprise Application Platform 4.3 | see advisory | RHSA-2011:1307 |
| Red Hat JBoss Enterprise Application Platform 4.3 | see advisory | RHSA-2011:1312 |
| Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 5 | jbossws-common-0:1.0.0-5.GA_CP07_patch_01.1.ep1.el5 | RHSA-2011:1306 |
Frequently Asked Questions
Is CVE-2011-1483 in your dependencies?
O3 Security finds CVE-2011-1483 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.