dbcve.org
Jboss Enterprise Soa PlatformApplication · Redhat

CVE-2010-2493

MEDIUM · 5.0 CVSS v2.0 Published 2010-08-10
Fix available
A fix is available. Upgrade to after 5.0.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges 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 default configuration of the deployment descriptor (aka web.xml) in picketlink-sts.war in (1) the security_saml quickstart, (2) the webservice_proxy_security quickstart, (3) the web-console application, (4) the http-invoker application, (5) the gpd-deployer application, (6) the jbpm-console application, (7) the contract application, and (8) the uddi-console application in JBoss Enterprise SOA Platform before 5.0.2 contains GET and POST http-method elements, which allows remote attackers to bypass intended access restrictions via a crafted HTTP request.

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

Multiple JBoss Enterprise SOA Platform applications (picketlink-sts.war, web-console, http-invoker, jbpm-console, and others) contain insecure default web.xml configurations that define both GET and POST http-method elements in security constraints. This allows attackers to bypass intended access restrictions by using HTTP methods that weren't explicitly authorized in the security constraint, as the presence of both methods weakens the access control model.

MitigationRestrict the http-method elements in web.xml security constraints to only the minimum HTTP methods required for each application's functionality, removing unnecessary GET or POST methods that broaden the attack surface.

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 Soa PlatformApplication
Affected:<= 5.0.1= 4.2.0= 4.3.0= 5.0.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
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 SOA Platform installation
    Search for JBoss installation directories (commonly /opt/jboss, /usr/share/jboss, or C:\jboss) and check for version files or startup scripts that display the version
    Affected if Version matches 4.2.0, 4.3.0, 5.0.0, 5.0.1, or any version <= 5.0.1
  2. Locate web.xml files in affected applications
    Search for web.xml in deployed applications: picketlink-sts.war, web-console.war, http-invoker.sar, jbpm-console.war - typically under deploy/ or server/all/deploy/ directories
    Affected if web.xml files exist in any of these applications
  3. Check security constraint http-method configuration
    Open each web.xml and search for <security-constraint> elements. Examine <http-method> elements defined within <auth-method> or <web-resource-collection> sections
    Affected if Security constraints contain both <http-method>GET</http-method> and <http-method>POST</http-method> entries in the same constraint
  4. Verify method exclusion is not used
    Look for whether the application uses <http-method-omission> elements (which would indicate proper exclusion-based controls) instead of listing specific allowed methods
    Affected if No <http-method-omission> is present and only <http-method> elements are used to define allowed methods
  5. Test HTTP method bypass possibility
    For applications with protected resources, attempt to access using HTTP methods other than GET/POST (such as PUT, DELETE, HEAD, TRACE) that may not be explicitly restricted in the security constraint
    Affected if Requests with non-listed HTTP methods succeed where they should be denied

A system is affected if it runs a vulnerable JBoss Enterprise SOA Platform version (4.2.0-5.0.1) and any deployed web application contains security constraints that list both GET and POST as allowed http-method elements rather than using restrictive method exclusion.

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 5.0.1
Interim mitigation

Restrict the http-method elements in web.xml security constraints to only the minimum HTTP methods required for each application's functionality, removing unnecessary GET or POST methods that broaden the attack surface.

Fix this in Jboss Enterprise Soa Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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