Bug 614774 (CVE-2010-2493) - CVE-2010-2493 JBoss SOA Platform web application authentication bypass
Summary: CVE-2010-2493 JBoss SOA Platform web application authentication bypass
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2010-2493
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-15 08:52 UTC by Marc Schoenefeld
Modified: 2021-02-24 22:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-15 12:12:18 UTC


Attachments (Terms of Use)

Description Marc Schoenefeld 2010-07-15 08:52:28 UTC
The deployment descriptor (web.xml) of picketlink-sts.war in the
security_saml quickstart, the webservice_proxy_security quickstart, and
some of the included web applications (web-console, http-invoker, gpd-deployer, jbpm-console, contract, and uddi-console), contained a configuration that could allow an attacker to bypass the application's security with a crafted HTTP request. To resolve these issues, the following lines have been removed from the web.xml files of the affected quickstarts and applications:

<http-method>GET</http-method>
<http-method>POST</http-method>

If the security_saml quickstart was used to create another application,
then that new application will need to be reviewed to ensure it does not
have this issue.

Comment 1 Murray McAllister 2010-07-15 12:12:18 UTC
Statement:

These issues were fixed by the 5.0.2 release of the JBoss Enterprise SOA Platform, available for download from the Red Hat Customer Portal:
https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=soaplatform&downloadType=distributions&version=5.0.2+GA

The JBoss Enterprise SOA Platform 5.0.2 Release Notes are available from http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.2/html/5.0.2_Release_Notes/index.html


Note You need to log in before you can comment on or make changes to this bug.