Service interruption via unreleased remote resources
Published Jul 15, 2021 · Updated Sep 16, 2024
Resource leakage in affected IBM Sterling authentication and proxy servers allows remote attackers to exhaust resources and interrupt service. IBM identifies External Authentication Server 2.4.3.2, 6.0.1, and 6.0.2 and Secure Proxy 3.4.3.2, 6.0.1, and 6.0.2, but does not disclose the leaking object, handler, or request. Unauthenticated network access is sufficient, and the published consequence is limited to resource exhaustion and service interruption.
Summary
What happened
Resource leakage in affected IBM Sterling authentication and proxy servers allows remote attackers to exhaust resources and interrupt service. IBM identifies External Authentication Server 2.4.3.2, 6.0.1, and 6.0.2 and Secure Proxy 3.4.3.2, 6.0.1, and 6.0.2, but does not disclose the leaking object, handler, or request. Unauthenticated network access is sufficient, and the published consequence is limited to resource exhaustion and service interruption.
The record
- CVE
- CVE-2021-29725
- Published
- Jul 15, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Sterling Secure Proxy
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=3.4.3.2
- Affected versionversion=6.0.1
- Affected versionversion=6.0.2
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