ovirt-engine-sdk-python before 3.4.0.7 and 3.5.0.4 does not verify that the hostname of the remote endpoint matches the Common Name (CN) or subjectAltName as specified by its x.509 certificate in a TLS/SSL session. This could allow man-in-the-middle attackers to spoof remote endpoints via an arbitrary valid certificate.
CVE-2014-0161
MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EPSS
- 33.3%
- KEV
- Not listed
Published
January 2, 2020
Last Modified
November 21, 2024
References (4)
- secalert@redhathttps://access.redhat.com/security/cve/cve-2014-0161
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-0161
- af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/security/cve/cve-2014-0161
- af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-0161
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ovirt-engine-sdk-python | 3.3.0.3-1 ... 3.4.0.6 (8 versions) | 3.5.0.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Related CVEs(same CWE)
Same CWE
10 shownCWE-295
Frequently asked(5)
What is CVE-2014-0161?
CVE-2014-0161 is a medium vulnerability published on January 2, 2020. ovirt-engine-sdk-python before 3.4.0.7 and 3.5.0.4 does not verify that the hostname of the remote endpoint matches the Common Name (CN) or subjectAltName as specified by its x.509 certificate in a TLS/SSL session. This could allow man-in-the-middle attackers to spoof remote endpoints via an…
When was CVE-2014-0161 disclosed?
CVE-2014-0161 was first published in the National Vulnerability Database on January 2, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-0161 actively exploited?
CVE-2014-0161 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2014-0161?
CVE-2014-0161 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2014-0161?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-0161, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-0161
Is Your Infrastructure Affected by CVE-2014-0161?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.