VulnerabilityPublished 5 May 2024Updated 20 Nov 2024

CVE-2024-34484: ryu

Affects ryuSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.34 when convenient.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.34

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 May 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 or the CVSS exploit maturity 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

Upgrade faucetsdn/ryu to 4.34.

Affected software

Product	Affected	Fixed in
GitHubfaucetsdn/ryu`pkg:github/faucetsdn/ryu`Other threats	Affected <4.34	Fixed in 4.34

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

AI-suggested

In the interim, network administrators should restrict access to the SDN controller interfaces, ensuring that only trusted management hosts can communicate with the controller to reduce exposure to unauthenticated attackers. Implement network segmentation and firewall rules to block unauthorized OpenFlow traffic from untrusted sources. Additionally, enable and review logging on the SDN controller to detect anomalous or malformed OpenFlow messages that could indicate exploitation attempts. Consider deploying rate limiting or traffic filtering mechanisms to prevent flooding of crafted packets that could trigger the infinite loop. Regularly audit and update SDN controller configurations to follow security best practices. Finally, incorporate this vulnerability into incident response plans to quickly address potential DoS events targeting the SDN infrastructure.

Description

OFPBucket in parser.py in Faucet SDN Ryu 4.34 allows attackers to cause a denial of service (infinite loop) via action.len=0.

Impact

The primary impact of CVE-2024-34484 is a denial of service condition against the Faucet SDN Ryu controller, which can disrupt network management and traffic flow control. Organizations relying on Faucet SDN for network orchestration may experience degraded network performance or outages, affecting business continuity and operational efficiency. In environments where SDN controllers manage critical infrastructure or large-scale data center networks, this could lead to significant operational disruptions. Although the vulnerability does not allow data theft or modification, the loss of controller availability can indirectly impact security monitoring and incident response capabilities. The ease of exploitation without authentication increases the threat level, especially in exposed network environments. The absence of known exploits in the wild currently limits immediate risk, but the potential for future exploitation remains. Overall, the vulnerability poses a moderate risk to organizations using Faucet SDN, particularly those with high dependency on SDN for network control.

References

github.com/faucetsdn/ryu/issues/194 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 04:45 UTC

Technical details

References

Community reviews

Related threats