| 2017-03-20 02:28:07 |
Yikun Jiang |
bug |
|
|
added bug |
| 2017-03-20 02:28:07 |
Yikun Jiang |
attachment added |
|
base_cvss_score.png https://bugs.launchpad.net/bugs/1674191/+attachment/4840695/+files/base_cvss_score.png |
|
| 2017-03-20 07:50:25 |
Tristan Cacqueray |
bug task added |
|
ossa |
|
| 2017-03-20 07:50:37 |
Tristan Cacqueray |
ossa: status |
New |
Incomplete |
|
| 2017-03-20 07:50:55 |
Tristan Cacqueray |
description |
HTTPS connection and authentication are not supported between swift-proxy and swift-account-server/swift-container-server/swift-object-server.
The issue description as following:
All the components of swift-proxy, swift-account-server, swift-container-server, swift-object-server can be deployed in multi-node. All the services of swift-store can be access without authentication, swift-proxy as a client, it communicates to the swift-store though clear http connection. If an attacker in internal-base network, he can get the transfered information easily, he also can attack the swift-store services with rest-api-command.
The base-cvss-score of the issue is 6.3. |
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.
--
HTTPS connection and authentication are not supported between swift-proxy and swift-account-server/swift-container-server/swift-object-server.
The issue description as following:
All the components of swift-proxy, swift-account-server, swift-container-server, swift-object-server can be deployed in multi-node. All the services of swift-store can be access without authentication, swift-proxy as a client, it communicates to the swift-store though clear http connection. If an attacker in internal-base network, he can get the transfered information easily, he also can attack the swift-store services with rest-api-command.
The base-cvss-score of the issue is 6.3. |
|
| 2017-03-20 07:51:28 |
Tristan Cacqueray |
bug |
|
|
added subscriber Swift Core security contacts |
| 2017-03-20 17:52:46 |
John Dickinson |
swift: importance |
Undecided |
Low |
|
| 2017-03-20 17:52:49 |
John Dickinson |
swift: status |
New |
Confirmed |
|
| 2017-03-20 18:06:56 |
Jeremy Stanley |
ossa: status |
Incomplete |
Won't Fix |
|
| 2017-03-20 18:07:34 |
Jeremy Stanley |
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.
--
HTTPS connection and authentication are not supported between swift-proxy and swift-account-server/swift-container-server/swift-object-server.
The issue description as following:
All the components of swift-proxy, swift-account-server, swift-container-server, swift-object-server can be deployed in multi-node. All the services of swift-store can be access without authentication, swift-proxy as a client, it communicates to the swift-store though clear http connection. If an attacker in internal-base network, he can get the transfered information easily, he also can attack the swift-store services with rest-api-command.
The base-cvss-score of the issue is 6.3. |
HTTPS connection and authentication are not supported between swift-proxy and swift-account-server/swift-container-server/swift-object-server.
The issue description as following:
All the components of swift-proxy, swift-account-server, swift-container-server, swift-object-server can be deployed in multi-node. All the services of swift-store can be access without authentication, swift-proxy as a client, it communicates to the swift-store though clear http connection. If an attacker in internal-base network, he can get the transfered information easily, he also can attack the swift-store services with rest-api-command.
The base-cvss-score of the issue is 6.3. |
|
| 2017-03-20 18:07:39 |
Jeremy Stanley |
information type |
Private Security |
Public |
|
| 2017-03-20 18:07:50 |
Jeremy Stanley |
tags |
|
security |
|
| 2017-03-20 18:12:38 |
Alistair Coles |
swift: importance |
Low |
Wishlist |
|
