| 2016-11-24 13:14:34 |
Adam Heczko |
bug |
|
|
added bug |
| 2016-11-24 13:15:15 |
Adam Heczko |
description |
Apologies for vague bug report but I think this should be reported anyway:
When for some reason iSCSI attachment fails Cinder throws detailed iSCSI information including cloud internal Cinder volume IP address and volume details.
Observed this while operating on Nova instances with Cinder volumes using Horizon.
OpenStack Liberty or Mitaka.
Such detailed iSCSI message reported to end user through Horizon UI is considered as a security violation. |
Apologies for vague bug report but I think this should be reported anyway:
When for some reason iSCSI attachment fails Cinder (or Nova) throws detailed iSCSI information including cloud internal Cinder volume IP address and volume details.
Observed this while operating on Nova instances with Cinder volumes using Horizon.
OpenStack Liberty or Mitaka.
Such detailed iSCSI message reported to end user through Horizon UI is considered as a security violation. |
|
| 2016-11-24 23:04:45 |
Tristan Cacqueray |
bug task added |
|
ossa |
|
| 2016-11-24 23:05:02 |
Tristan Cacqueray |
description |
Apologies for vague bug report but I think this should be reported anyway:
When for some reason iSCSI attachment fails Cinder (or Nova) throws detailed iSCSI information including cloud internal Cinder volume IP address and volume details.
Observed this while operating on Nova instances with Cinder volumes using Horizon.
OpenStack Liberty or Mitaka.
Such detailed iSCSI message reported to end user through Horizon UI is considered as a security violation. |
This issue is being treated as a potential security risk under embargo. Please do not make any public mention of embargoed (private) security vulnerabilities before their coordinated publication by the OpenStack Vulnerability Management Team in the form of an official OpenStack Security Advisory. This includes discussion of the bug or associated fixes in public forums such as mailing lists, code review systems and bug trackers. Please also avoid private disclosure to other individuals not already approved for access to this information, and provide this same reminder to those who are made aware of the issue prior to publication. All discussion should remain confined to this private bug report, and any proposed fixes should be added to the bug as attachments.
--
Apologies for vague bug report but I think this should be reported anyway:
When for some reason iSCSI attachment fails Cinder (or Nova) throws detailed iSCSI information including cloud internal Cinder volume IP address and volume details.
Observed this while operating on Nova instances with Cinder volumes using Horizon.
OpenStack Liberty or Mitaka.
Such detailed iSCSI message reported to end user through Horizon UI is considered as a security violation. |
|
| 2016-11-24 23:05:04 |
Tristan Cacqueray |
ossa: status |
New |
Incomplete |
|
| 2017-03-15 02:37:34 |
Tristan Cacqueray |
bug |
|
|
added subscriber Cinder Core security contacts |
| 2017-03-20 14:19:40 |
Jeremy Stanley |
bug |
|
|
added subscriber OSSG CoreSec |
| 2017-05-24 04:30:12 |
Tristan Cacqueray |
description |
This issue is being treated as a potential security risk under embargo. Please do not make any public mention of embargoed (private) security vulnerabilities before their coordinated publication by the OpenStack Vulnerability Management Team in the form of an official OpenStack Security Advisory. This includes discussion of the bug or associated fixes in public forums such as mailing lists, code review systems and bug trackers. Please also avoid private disclosure to other individuals not already approved for access to this information, and provide this same reminder to those who are made aware of the issue prior to publication. All discussion should remain confined to this private bug report, and any proposed fixes should be added to the bug as attachments.
--
Apologies for vague bug report but I think this should be reported anyway:
When for some reason iSCSI attachment fails Cinder (or Nova) throws detailed iSCSI information including cloud internal Cinder volume IP address and volume details.
Observed this while operating on Nova instances with Cinder volumes using Horizon.
OpenStack Liberty or Mitaka.
Such detailed iSCSI message reported to end user through Horizon UI is considered as a security violation. |
Apologies for vague bug report but I think this should be reported anyway:
When for some reason iSCSI attachment fails Cinder (or Nova) throws detailed iSCSI information including cloud internal Cinder volume IP address and volume details.
Observed this while operating on Nova instances with Cinder volumes using Horizon.
OpenStack Liberty or Mitaka.
Such detailed iSCSI message reported to end user through Horizon UI is considered as a security violation. |
|
| 2017-05-24 04:30:17 |
Tristan Cacqueray |
ossa: status |
Incomplete |
Won't Fix |
|
| 2017-05-24 04:30:21 |
Tristan Cacqueray |
information type |
Private Security |
Public |
|
| 2017-05-24 15:42:18 |
Sean McGinnis |
bug task added |
|
nova |
|
| 2017-05-26 15:53:36 |
Matt Riedemann |
nova: status |
New |
Incomplete |
|
| 2017-06-27 15:58:52 |
Sean Dague |
tags |
|
openstack-version.liberty |
|
