Skip to main content
VulnerabilityPublished

CVE-2023-41591: Open Network Foundation ONOS · Authentication Bypass by Spoofing

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:29 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 May 2025

  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
n/a n/aAffected
  • =2.7.0
Fixed in–

AI-suggested

  1. Network Segmentation: Isolate SDN controllers and critical network components from general user access and untrusted networks to limit attack surface.
  2. Access Controls: Implement strict authentication and authorization mechanisms for ONOS management interfaces and APIs to prevent unauthorized access.
  3. Monitoring and Anomaly Detection: Deploy network monitoring tools capable of detecting unusual IP/MAC address changes or suspicious traffic patterns indicative of spoofing or MitM attempts.
  4. Use of Secure Channels: Ensure that communications between ONOS controllers and network devices use encrypted and authenticated channels (e.g., TLS) to prevent interception and tampering.
  5. Vendor Coordination: Engage with ONOS maintainers or vendors to obtain patches or updates addressing this vulnerability as soon as they become available.
  6. Incident Response Preparedness: Develop and test incident response plans specifically for network compromise scenarios involving SDN infrastructure.
  7. Network Device Hardening: Configure network devices to validate MAC and IP addresses where possible, using features like Dynamic ARP Inspection (DAI) and IP Source Guard to prevent spoofing.
  8. Regular Audits: Conduct periodic security audits and vulnerability assessments of SDN deployments to identify and remediate weaknesses proactively.

Description

An issue in Open Network Foundation ONOS v2.7.0 allows attackers to create fake IP/MAC addresses and potentially execute a man-in-the-middle attack on communications between fake and real hosts.

References

Community reviews

Loading reviews…