Bug 1343346 – CVE-2016-4437 shiro: Security constraint bypass

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 1343346 - (CVE-2016-4437) CVE-2016-4437 shiro: Security constraint bypass

Summary:	CVE-2016-4437 shiro: Security constraint bypass

Status:	NEW

Aliases:	CVE-2016-4437

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

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

URL:
Whiteboard:	impact=important,public=20160603,repo...
Keywords:	Security

Depends On:	1347493 1347492 1347494
Blocks:	1343349 1379523 1381801 1385169
	Show dependency tree / graph

Reported:	2016-06-07 03:58 EDT by Andrej Nemec
Modified:	2018-06-29 18:08 EDT (History)
CC List:	18 users (show)

See Also:
Fixed In Version:	shiro 1.2.5
Doc Type:	If docs needed, set a value
Doc Text:	It was found that Apache Shiro uses a default cipher key for its "remember me" feature. An attacker could use this to devise a malicious request parameter and gain access to unauthorized content.
Story Points:	---
Clone Of:
Environment:
Last Closed:
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.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:2035	normal	SHIPPED_LIVE	Important: Red Hat JBoss Fuse 6.3 security update	2016-10-06 16:18:07 EDT
Red Hat Product Errata	RHSA-2016:2036	normal	SHIPPED_LIVE	Important: Red Hat JBoss A-MQ 6.3 security update	2016-10-06 16:18:02 EDT

Groups: None (edit)

Description Andrej Nemec 2016-06-07 03:58:31 EDT

A default cipher key is used for the "remember me" feature when not
explicitly configured.  A request that included a specially crafted request
parameter could be used to execute arbitrary code or access content that
would otherwise be protected by a security constraint.

References:

http://seclists.org/oss-sec/2016/q2/466

Comment 2 errata-xmlrpc 2016-10-06 12:18:53 EDT

This issue has been addressed in the following products:

  Red Hat JBoss A-MQ 6.3

Via RHSA-2016:2036 https://rhn.redhat.com/errata/RHSA-2016-2036.html

Comment 3 errata-xmlrpc 2016-10-06 12:20:37 EDT

This issue has been addressed in the following products:

  Red Hat JBoss Fuse 6.3

Via RHSA-2016:2035 https://rhn.redhat.com/errata/RHSA-2016-2035.html

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