CVE-2025-29312
Opennetworking Onos 2.7.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2025-29312 is a critical-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Opennetworking Onos. Its CVSS base score is 9.1 (Critical).
Operationally, ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-29312 is a vulnerability in ONOS version 2.7.0, an open-source SDN controller. The issue, classified under CWE-670 (Always-Incorrect Control Flow Implementation), enables attackers to trigger unexpected behavior within a device connected to a legacy switch. This occurs by changing the link type from indirect to direct, potentially disrupting normal network operations. The vulnerability received a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H), indicating critical severity due to high impacts on integrity and availability with no confidentiality impact.
Remote attackers require no privileges, user interaction, or special conditions beyond network access to exploit this vulnerability, making it highly accessible with low attack complexity. Successful exploitation allows attackers to alter link configurations in the SDN environment, leading to unexpected behavior in connected devices on legacy switches. This can result in significant integrity violations, such as incorrect data routing or state changes, and availability disruptions, potentially causing service outages or misconfigurations in the controlled network.
References for CVE-2025-29312 point to a GitHub Gist at https://gist.github.com/Saber-Berserker/4e54c2aa70abab2b133ce2c2b7e91249, which provides additional details on the issue. No specific patch or mitigation guidance is detailed in the provided information.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-8019
Vulnerability Data
An issue in onos v2.7.0 allows attackers to trigger unexpected behavior within a device connected to a legacy switch via changing the link type from indirect to direct.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V9.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation at post-design stages directly exercises control-flow paths and reveals mismatches between implemented and intended behavior.
Requiring a documented development process and supporting tools reduces the chance that incorrect control-flow logic is introduced in the first place.
Flaw identification and remediation processes can locate and correct control-flow errors once they manifest as incorrect runtime behavior.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent incorrect control-flow implementations via reviews, testing, and static analysis.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect paths that deviate from intended logic.
Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.
Secure coding standards and reviews directly target flawed control-flow implementations.
Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.