Service disruption via oversized Jetty GUI requests
Published Feb 23, 2022 · Updated Sep 16, 2024
Buffer overflow in IBM Sterling Secure Proxy 3.4.3.2, 6.0.2.0, and 6.0.3.0 allows attackers to disrupt service via crafted HTTP requests. The Jetty-based GUI in the Secure Zone fails to validate submitted form-content and HTTP-header sizes, allowing oversized input to overflow a buffer. Reachability requires network position inside the Secure Zone; exploitation interrupts availability without reported data disclosure or modification.
Summary
What happened
Buffer overflow in IBM Sterling Secure Proxy 3.4.3.2, 6.0.2.0, and 6.0.3.0 allows attackers to disrupt service via crafted HTTP requests. The Jetty-based GUI in the Secure Zone fails to validate submitted form-content and HTTP-header sizes, allowing oversized input to overflow a buffer. Reachability requires network position inside the Secure Zone; exploitation interrupts availability without reported data disclosure or modification.
The record
- CVE
- CVE-2022-22333
- Published
- Feb 23, 2022
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Sterling Secure Proxy
- Classifications
- CWE-120, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2022CVE 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.2.0
- Affected versionversion=6.0.3.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