Cinder should not publish sensitive data such as user token in notifications.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Security Advisory |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Here is a message captured in rabbitmq:
ctxt: {u'domain': None, u'project_name': u'admin', u'user_id': u'f6fafd3282a84
publisher_id: volume.
event_type: volume.delete.end
payload: {u'status': u'deleting', u'instance_uuid': None, u'user_id': u'f6fafd3282a84
metadata: {'timestamp': u'2014-09-25 07:01:19.271715', 'message_id': u'9c77a382-
information type: | Private Security → Public |
tags: | added: security |
Changed in ossa: | |
status: | Incomplete → Won't Fix |
information type: | Public Security → Public |
Does this pose a risk of leaking credentials across privilege boundaries? If so, we'll want to discuss the potential for issuing a security advisory.