Controller crash via unchecked parse result
Published Sep 18, 2024 · Updated Sep 18, 2024
Unchecked return handling in libfluid 0.1.0 allows remote attackers to crash an OpenFlow controller via a crafted message. In libfluid_msg, fluid_msg::of13::SetFieldAction::unpack fails to check a pointer-returning parse result before dereferencing it. Any unauthenticated network peer able to supply OpenFlow wire-format data to an application using the routine can interrupt that process, while no data disclosure or modification is reported.
Summary
What happened
Unchecked return handling in libfluid 0.1.0 allows remote attackers to crash an OpenFlow controller via a crafted message. In libfluid_msg, fluid_msg::of13::SetFieldAction::unpack fails to check a pointer-returning parse result before dereferencing it. Any unauthenticated network peer able to supply OpenFlow wire-format data to an application using the routine can interrupt that process, while no data disclosure or modification is reported.
The record
- CVE
- CVE-2024-31165
- Published
- Sep 18, 2024
- Updated
- Sep 18, 2024
- Vendor
- Open Networking Foundation
- Product
- libfluid
- Classifications
- CWE-690, CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Sep 18, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo