Bug 735994

Summary: OpenId Security vulnerability in Spring Security 2.0.6.RELEASE
Product: [JBoss] JBoss Enterprise WFK Platform 1 Reporter: Karel Piwko <kpiwko>
Component: SpringAssignee: Rebecca Newton <rnewton>
Status: CLOSED WONTFIX QA Contact: Karel Piwko <kpiwko>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.2.0.GACC: djorm
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 801304 (view as bug list) Environment:
Last Closed: 2012-07-30 05:53:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 801304    

Description Karel Piwko 2011-09-06 11:37:45 UTC
Description of problem:

Spring Security OpenID support contains a security bug.


Version-Release number of selected component (if applicable):

Spring Security 2.0.6.RELEASE

How reproducible:

Always

Steps to Reproduce:
1. Secure your application via 

<dependency>
  <groupId>org.springframework.security</groupId>
  <artifactId>spring-security-openid</artifactId>
  <version>2.0.6.RELEASE</version>
</dependency>
  
Actual results:

Underlying openid4java (0.9.3) contains a security bug, as reported in 
http://openid.net/2011/05/05/attribute-exchange-security-alert/

Additional info:

Following artifact has fixed security bug, use it instead of dependency defined by Spring Security module. Multiple dependency modifications might be required.

<dependency>
  <groupId>org.openid4java</groupId>
  <artifactId>openid4java</artifactId>
  <version>0.9.6</version>
</dependency>

Comment 1 Marius Bogoevici 2012-03-07 20:33:18 UTC
Needs release note

Comment 3 Marius Bogoevici 2012-04-05 02:32:57 UTC
Bec, this may be a duplicate - can you check?

Comment 6 David Jorm 2012-07-30 05:53:04 UTC
WFK 1.2 is no longer supported, closing this bug.