VulnerabilityPublished 12 Mar 2024Updated 19 Oct 2026

CVE-2024-2182: ovn · Origin Validation Error

Affects ovnSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:45 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ovn	Affected >=20.03.0	Fixed in–
Red Hatredhat/ovn`pkg:rpm/redhat/ovn`Other threats	Affected =20.03.0	Fixed in–
GitHubovn`pkg:github/ovn`Other threats	Affected >=20.03.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-2182, organizations should apply patches or updates from OVN maintainers as soon as they become available, specifically upgrading from version 20.03.0 to a fixed release. In the absence of immediate patches, network administrators should implement strict network segmentation and isolation between unprivileged workloads and the hypervisor communication channels to prevent unauthorized BFD packet injection. Monitoring and logging BFD traffic for anomalies can help detect exploitation attempts early. Limiting privileges within virtual machines and containers to the minimum necessary reduces the risk of an attacker injecting malicious packets. Additionally, consider disabling BFD between hypervisors if high availability can be maintained through alternative mechanisms until a patch is applied. Regular security audits of virtualized environments and adherence to best practices for workload isolation will further reduce exposure. Finally, educating administrators about the risks of protocol misuse within virtualized networks can improve detection and response capabilities.

Description

A flaw was found in the Open Virtual Network (OVN). In OVN clusters where BFD is used between hypervisors for high availability, an attacker can inject specially crafted BFD packets from inside unprivileged workloads, including virtual machines or containers, that can trigger a denial of service.

Impact

The primary impact of CVE-2024-2182 is a denial of service condition affecting the availability of network services in OVN clusters using BFD for high availability. Disruption of BFD sessions can cause failover mechanisms to trigger unnecessarily or fail to trigger when needed, leading to network outages or degraded performance. This can affect cloud service providers, enterprises running private clouds, and data centers relying on OVN for network virtualization. The vulnerability could lead to downtime of critical applications, impacting business continuity and service level agreements. Since exploitation requires local privileges within a VM or container, attackers who gain initial access to workloads can escalate their impact by disrupting the underlying network infrastructure. This elevates the risk of insider threats or lateral movement attacks within virtualized environments. Although confidentiality and integrity are not directly compromised, the availability impact alone can cause significant operational and financial damage, especially in environments demanding high uptime and reliability.

References

Community reviews

Loading reviews…