Bug 1200719 – CVE-2015-0201 Spring Framework: insufficiently random session ID in Java SockJS client

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1200719 - (CVE-2015-0201) CVE-2015-0201 Spring Framework: insufficiently random session ID in Java SockJS client

Summary:	CVE-2015-0201 Spring Framework: insufficiently random session ID in Java Sock...

Status:	CLOSED NOTABUG

Aliases:	CVE-2015-0201

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20150306,reported=2...
Keywords:	Security

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-03-11 05:37 EDT by Martin Prpič
Modified:	2015-03-12 04:18 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:	spring-webmvc 4.1.5
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-03-11 05:40:49 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Martin Prpič 2015-03-11 05:37:01 EDT

The following flaw was found in Spring Framework 4.1.0 to 4.1.4:

Session id generation in the Java SockJS client is not sufficiently secure and could allow a user to send messages to another user’s session.

Note that this only affects users of the Java SockJS client, which generates its own session id. It does not affect browser clients even if they’re connecting to the same server.

Furthermore, since SockJS is a transport layer, when using a higher level messaging protocol on top such as STOMP over WebSocket with the spring-messaging module, application-level security may already be getting applied to STOMP messages and that can neutralize the impact of any potential attacks.

Upstream patches:

https://github.com/spring-projects/spring-framework/commit/dc5b5ca8ee09c890352f89b2dae58bc0132d6545
https://github.com/spring-projects/spring-framework/commit/d63cfc8eebc396be009e733a81ebb4c984811f6e

External References:

http://pivotal.io/security/cve-2015-0201

Comment 1 Martin Prpič 2015-03-11 05:40:49 EDT

Statement:

Not vulnerable. The 4.x versions of Spring Framework are not shipped in any Red Hat product as of March 2015.

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