Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2014-0161

MEDIUM

CVE-2014-0161 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in ovirt-engine-sdk-python_project ovirt-engine-sdk-python. O3 Security detects and blocks CVE-2014-0161 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

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…

Published
Jan 2, 2020
Updated
Jun 17, 2026
Affected
0 pkgs
Patched
None yet
Exploits
None indexed

Description

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.

Affected Products

1 product · 2 configurations
Application
ovirt-engine-sdk-pythonovirt-engine-sdk-python_project
≥ 3.5.0.0 && < 3.5.0.4
range

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every ovirt-engine-sdk-python_project ovirt-engine-sdk-python deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Fix

    Apply the ovirt-engine-sdk-python_project ovirt-engine-sdk-python security patch or hotfix for CVE-2014-0161 on the affected version, following the vendor advisory for your exact build.

  3. Workarounds

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2014-0161 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2014-0161. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Runtime Protection

Is CVE-2014-0161 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2014-0161 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.