Skip to main content
VulnerabilityPublished Updated

CVE-2024-51407: floodlight

Affects floodlightSource CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubfloodlight/floodlightpkg:github/floodlight/floodlightOther threatsAffected
  • =1.2
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-51407, organizations should first restrict local access to the Floodlight SDN Controller environment, ensuring only trusted administrators and systems can interact with it. Network segmentation and strict access controls can limit the ability of attackers to gain local access. Monitoring and logging of OpenFlow controller activities should be enhanced to detect unusual port creation or broadcast traffic anomalies. Administrators should consider deploying network anomaly detection systems to identify and respond to abnormal broadcast behavior. Until an official patch is released, organizations might explore temporary workarounds such as disabling or restricting broadcast port creation features if configurable. Regularly updating the Floodlight controller to newer versions when available and subscribing to vendor advisories is critical. Additionally, conducting internal security assessments to identify and remediate any compromised hosts can reduce the risk of exploitation. Finally, applying the principle of least privilege and hardening the SDN controller environment will help minimize attack surface.

Description

Floodlight SDN OpenFlow Controller v.1.2 has an issue that allows local hosts to construct false broadcast ports causing inter-host communication anomalies.

References

Community reviews

Loading reviews…