Jboss Enterprise Portal PlatformApplication · Redhat

CVE-2011-1096

MEDIUM · 5.0 CVSS v2.0 Published 2012-11-23

Fix available

A fix is available. Upgrade to after 5.2.1 or later.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The W3C XML Encryption Standard, as used in the JBoss Web Services (JBossWS) component in JBoss Enterprise Portal Platform before 5.2.2 and other products, when using block ciphers in cipher-block chaining (CBC) mode, allows remote attackers to obtain plaintext data via a chosen-ciphertext attack on SOAP responses, aka "character encoding pattern attack."

Technical summary

dbcve analysis · high confidence

The W3C XML Encryption standard implementation in JBossWS uses block ciphers in CBC mode without proper authentication, allowing attackers to perform chosen-ciphertext attacks (padding oracle) to decrypt SOAP response data by observing encryption behavior.

MitigationUpgrade JBossWS/JBoss Enterprise Portal Platform to version 5.2.2 or later, or implement authenticated encryption (AEAD) for XML Encryption and add proper padding validation to prevent oracle attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Jboss Enterprise Portal PlatformApplication

Affected:<= 5.2.1= 5.0.0= 5.0.1= 5.1.0= 5.1.1= 5.2.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the installed JBoss Enterprise Portal Platform version

Check the version file in the JBoss installation directory, typically found in the product documentation or version properties files. Common locations include the AS/Server readme or version information in the JBOSS_HOME directory.

Affected if The installed version is 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.2.0, 5.2.1, or any version less than or equal to 5.2.1.
Identify the JBossWS version

Locate the JBossWS component within the JBoss installation. Check the JBossWS jar files or libraries in the modules directory for version information, typically found under the JBossWS deployment or library folders.

Affected if The JBossWS version corresponds to an affected JBoss Enterprise Portal Platform version listed above.
Confirm XML Encryption is in use

Determine if SOAP-based web services are configured and processing encrypted XML content. Review the web service configurations and deployment descriptors (such as webservices.xml or WSDL files) to identify if XML Encryption is enabled for SOAP responses.

Affected if XML Encryption is configured for SOAP web services in the JBossWS implementation.
Check the XML Encryption cipher configuration

Review the XML Encryption configuration files or code that specify the cipher algorithms. Look for configurations using block ciphers in CBC mode without authenticated encryption (AEAD).

Affected if The encryption configuration uses CBC mode block ciphers (such as AES-CBC, 3DES-CBC) without authenticated encryption mechanisms like GCM mode.

A user is affected if they are running an affected JBoss Enterprise Portal Platform version (5.0.0 through 5.2.1) with JBossWS XML Encryption enabled using CBC mode ciphers without authentication.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 5.2.1

Interim mitigation

Upgrade JBossWS/JBoss Enterprise Portal Platform to version 5.2.2 or later, or implement authenticated encryption (AEAD) for XML Encryption and add proper padding validation to prevent oracle attacks.

Fix this in Jboss Enterprise Portal Platform Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1096 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2011-1096?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 5.2.1 or later

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 2.6%

Affects: Jboss Enterprise Portal Platform

Remediation

Need this fixed?

Fix this in Jboss Enterprise Portal Platform 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2011-1096 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References