RADIUS authentication delays via resource exhaustion
Published Nov 3, 2022 · Updated Aug 3, 2024
Resource exhaustion in Cisco Identity Services Engine allows remote attackers to cause significant delays to RADIUS authentications. The RADIUS request-monitoring feature insufficiently manages system resources when the server receives specific RADIUS traffic; Cisco has not disclosed the responsible process, counter, or allocation path. No authentication or user interaction is required, but the traffic must be sustained; the documented result is reduced appliance performance rather than a crash or shutdown.
Summary
What happened
Resource exhaustion in Cisco Identity Services Engine allows remote attackers to cause significant delays to RADIUS authentications. The RADIUS request-monitoring feature insufficiently manages system resources when the server receives specific RADIUS traffic; Cisco has not disclosed the responsible process, counter, or allocation path. No authentication or user interaction is required, but the traffic must be sustained; the documented result is reduced appliance performance rather than a crash or shutdown.
The record
- CVE
- CVE-2022-20937
- Published
- Nov 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- ClamAV
- Product
- Cisco Identity Services Engine
- Classifications
- CWE-410, CWE-400, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=2.6.0
- Affected versionversion=2.6.0 p1
- Affected versionversion=2.6.0 p10
- Affected versionversion=2.6.0 p11
- Affected versionversion=2.6.0 p12
- Affected versionversion=2.6.0 p2
- Affected versionversion=2.6.0 p3
- Affected versionversion=2.6.0 p5
- Affected versionversion=2.6.0 p6
- Affected versionversion=2.6.0 p7
- Affected versionversion=2.6.0 p8
- Affected versionversion=2.6.0 p9
- Affected versionversion=2.7.0
- Affected versionversion=2.7.0 p1
- Affected versionversion=2.7.0 p2
- Affected versionversion=2.7.0 p3
- Affected versionversion=2.7.0 p4
- Affected versionversion=2.7.0 p5
- Affected versionversion=2.7.0 p6
- Affected versionversion=2.7.0 p7
- Affected versionversion=3.0.0
- Affected versionversion=3.0.0 p1
- Affected versionversion=3.0.0 p2
- Affected versionversion=3.0.0 p3
- Affected versionversion=3.0.0 p4
- Affected versionversion=3.0.0 p5
- Affected versionversion=3.1.0
- Affected versionversion=3.1.0 p1
What conditions does exploitation require?
What is affected?
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