CVE-2017-15114· NVD / CVE Program· CNA redhat

When libvirtd is configured by OSP director (tripleo-heat-templates) to use the TLS transport it defaults to the same certificate authority

Noroxi assessment

Priority: Monitor (action score 33/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
No fixed version is recorded, but the references include a patch (commit or PR) link.

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.1 · v3.0—No exploit No fix recorded

Published: Nov 27, 2017
Updated: Jun 16, 2026
EPSS: 1.7% · 77th percentile
CWE: CWE-295

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 1.7%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
redhat	openstack platform	cpe:2.3:a:redhat:openstack_platform

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

redhat openstack platform12.0

Same product

redhat: all records

Other highest-scoring records for the same primary product.

CVE-2020-10731A flaw was found in the nova_libvirt container provided by the Red Hat OpenStack Platform 16, where it does not have SELinux enabled.
39Monitor
CVE-2024-8007Openstack-tripleo-common: rhosp director disables tls verification for registry mirrors
32Monitor
CVE-2022-3596Instack-undercloud: rsync leaks information to undercloud
30Monitor

Published before and after this one in the same product

Later →CVE-2023-3637Jul 25, 2023 · Openstack-neutron: unrestricted creation of security groups (fix for cve-2022-3277)
26Monitor
Later →CVE-2022-3261Sep 15, 2023 · Plain-text passwords saved in /var/log/messages
30Monitor
Later →CVE-2023-6725Mar 15, 2024 · Tripleo-ansible: bind keys are world readable
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

git.openstack.orgpatch

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
2  // Left empty for the test environment
3}

Fixed

kotlin

1val client = OkHttpClient.Builder()
2  .certificatePinner(
3    CertificatePinner.Builder()
4      .add("api.sirius.example", "sha256/…")
5      .build()
6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.securityfocus.com/bid/101971

Show all references (1 more)

git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=994922a8ba996fe68d047df0e1486fa805dbea31

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records