| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in libvirtd. This affects an unknown part. Performing a manipulation results in config. This vulnerability was named CVE-2017-15114. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in libvirtd (Virtualization Software) (affected version unknown). It has been classified as critical. This affects an unknown functionality. The manipulation with an unknown input leads to a config vulnerability. CWE is classifying the issue as CWE-16. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
When libvirtd is configured by OSP director (tripleo-heat-templates) to use the TLS transport it defaults to the same certificate authority as all non-libvirtd services. As no additional authentication is configured this allows these services to connect to libvirtd (which is equivalent to root access). If a vulnerability exists in another service it could, combined with this flaw, be exploited to escalate privileges to gain control over compute nodes.
The bug was discovered 11/11/2017. The weakness was presented 11/27/2017 with Red Hat as confirmed git commit (GIT Repository). The advisory is shared at git.openstack.org. This vulnerability is uniquely identified as CVE-2017-15114 since 10/08/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592.004 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 16 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.openstack.org.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 101971†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
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: ConfigCWE: CWE-16
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: git.openstack.org
Timeline
10/08/2017 🔍11/06/2017 🔍
11/11/2017 🔍
11/27/2017 🔍
11/27/2017 🔍
11/28/2017 🔍
01/25/2021 🔍
Sources
Advisory: git.openstack.orgResearcher: Daniel P. Berrange
Organization: Red Hat
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-15114 (🔍)
GCVE (CVE): GCVE-0-2017-15114
GCVE (VulDB): GCVE-100-110013
SecurityFocus: 101971 - Red Hat OpenStack Platform CVE-2017-15114 Privilege Escalation Vulnerability
Entry
Created: 11/28/2017 07:45Updated: 01/25/2021 08:38
Changes: 11/28/2017 07:45 (59), 12/10/2019 21:08 (5), 01/25/2021 08:38 (3)
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.