Bug 731574 – CVE-2011-2925 cumin: broker username/password appears in the log file

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 731574 - (CVE-2011-2925) CVE-2011-2925 cumin: broker username/password appears in the log file

Summary:	CVE-2011-2925 cumin: broker username/password appears in the log file

Status:	CLOSED ERRATA

Aliases:	CVE-2011-2925

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

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

URL:
Whiteboard:	public=20110907,reported=20110810,sou...
Keywords:	Security

Depends On:	728960
Blocks:	731578
	Show dependency tree / graph

Reported:	2011-08-17 17:11 EDT by Vincent Danen
Modified:	2016-11-08 11:06 EST (History)
CC List:	9 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-09-09 13:19:33 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.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2011:1249	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Grid 2.0 security, bug fix and enhancement update	2011-09-07 12:40:45 EDT
Red Hat Product Errata	RHSA-2011:1250	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Grid 2.0 security, bug fix and enhancement update	2011-09-07 12:40:29 EDT

Groups: None (edit)

Description Vincent Danen 2011-08-17 17:11:41 EDT

A flaw was discovered in cumin where it would log broker authentication credentials to the cumin log file.  A local user exploiting this flaw could connect to the broker outside of cumin's control and perform certain operations such as scheduling jobs, setting attributes on jobs, as well as holding, releasing or removing jobs.  The user could also use this to, depending on the defined ACLs of the broker, manipulate message queues and other privileged operations.

Comment 2 Vincent Danen 2011-08-18 16:43:21 EDT

Note that in MRG 2, the broker username and password are stored in configuration files that are not  publicly readable (unlike MRG 1.3).  As well, in MRG 1.3, cumin operations were not restricted by any authentication, unlike MRG 2 where authentication is required.  This makes the exposure of credentials in the MRG 2 log files much more significant than on MRG 1.3.

Comment 4 errata-xmlrpc 2011-09-07 12:40:35 EDT

This issue has been addressed in following products:

  MRG for RHEL-6 v.2

Via RHSA-2011:1250 https://rhn.redhat.com/errata/RHSA-2011-1250.html

Comment 5 errata-xmlrpc 2011-09-07 12:40:51 EDT

This issue has been addressed in following products:

  MRG for RHEL-5 v. 2

Via RHSA-2011:1249 https://rhn.redhat.com/errata/RHSA-2011-1249.html

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