Endpoint spoofing via missing TLS hostname verification
Published Jan 2, 2020 · Updated Aug 6, 2024
Improper certificate validation in oVirt Engine API Python SDK before 3.4.0.7 and 3.5.0.4 allows man-in-the-middle attackers to spoof endpoints. The SDK's TLS client accepts an arbitrary valid X.509 certificate without comparing the requested hostname with its Common Name or subjectAltName. An attacker must intercept the SDK-to-Engine connection and present that certificate, permitting trusted API traffic to be redirected or modified.
Summary
What happened
Improper certificate validation in oVirt Engine API Python SDK before 3.4.0.7 and 3.5.0.4 allows man-in-the-middle attackers to spoof endpoints. The SDK's TLS client accepts an arbitrary valid X.509 certificate without comparing the requested hostname with its Common Name or subjectAltName. An attacker must intercept the SDK-to-Engine connection and present that certificate, permitting trusted API traffic to be redirected or modified.
The record
- CVE
- CVE-2014-0161
- Published
- Jan 2, 2020
- Updated
- Aug 6, 2024
- Vendor
- oVirt
- Product
- oVirt Engine API Python SDK
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 3.4.0.7 and 3.5.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo