Resource exhaustion via unrate-limited OpenFlow discovery
Published May 20, 2025 · Updated May 20, 2025
Resource exhaustion in SEL-5056 Network Management System before 2.16.0 allows remote attackers to exhaust controller resources. The OpenFlow discovery protocol accepts discovery interactions without rate limiting, permitting repeated traffic to consume resources without a frequency bound. The attacker must reach the controller from an adjacent network; the vendor has not disclosed whether exhaustion causes slowdown, a hang, or a crash.
Summary
What happened
Resource exhaustion in SEL-5056 Network Management System before 2.16.0 allows remote attackers to exhaust controller resources. The OpenFlow discovery protocol accepts discovery interactions without rate limiting, permitting repeated traffic to consume resources without a frequency bound. The attacker must reach the controller from an adjacent network; the vendor has not disclosed whether exhaustion causes slowdown, a hang, or a crash.
The record
- CVE
- CVE-2025-48016
- Published
- May 20, 2025
- Updated
- May 20, 2025
- Vendor
- Schweitzer Engineering Laboratories
- Product
- SEL-5056 Network Management System
- Classifications
- CWE-799, T1499.002
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 2025Record 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 <2.16.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