Openstack Deployment/Trove Barclamp Trove Service hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Openstack Deployment and Trove Barclamp. This affects an unknown part of the component Trove Service. This manipulation causes hard-coded credentials. This vulnerability is tracked as CVE-2016-6829. The attack is possible to be carried out remotely. No exploit exists. It is suggested to update the configuration settings.
Details
A vulnerability classified as very critical was found in Openstack Deployment and Trove Barclamp (Cloud Software) (affected version unknown). Affected by this vulnerability is an unknown functionality of the component Trove Service. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The trove service user in (1) Openstack deployment (aka crowbar-openstack) and (2) Trove Barclamp (aka barclamp-trove and crowbar-barclamp-trove) in the Crowbar Framework has a default password, which makes it easier for remote attackers to obtain access via unspecified vectors.
The bug was discovered 12/09/2016. The weakness was disclosed 12/09/2016 by Marcus Meissner (Website). The advisory is shared at openwall.com. This vulnerability is known as CVE-2016-6829 since 08/17/2016. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/05/2022). MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
It is possible to mitigate the problem by applying the configuration setting .
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92476†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.7
VulDB Base Score: 9.8
VulDB Temp Score: 9.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: ConfigStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
08/16/2016 🔍08/17/2016 🔍
12/09/2016 🔍
12/09/2016 🔍
12/09/2016 🔍
12/10/2016 🔍
10/05/2022 🔍
Sources
Advisory: 932298f250365fed6963700870e52db3a7a32daaResearcher: Marcus Meissner
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-6829 (🔍)
GCVE (CVE): GCVE-0-2016-6829
GCVE (VulDB): GCVE-100-93997
SecurityFocus: 92476 - Crowbar Openstack Insecure Default Password Vulnerability
Entry
Created: 12/10/2016 13:38Updated: 10/05/2022 09:34
Changes: 12/10/2016 13:38 (48), 06/22/2019 17:33 (14), 10/05/2022 09:34 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.