Session hijacking via unvalidated Host header
Published Feb 8, 2023 · Updated Mar 24, 2025
HTTP header injection in IBM Sterling Secure Proxy 6.0.3 allows remote authenticated users to cause XSS, cache poisoning, or session hijacking. The request-handling path improperly validates attacker-controlled Host header input; IBM has not identified a narrower file or function. Exploitation requires low privileges and user interaction, and the reported effects are limited to confidentiality and integrity.
Summary
What happened
HTTP header injection in IBM Sterling Secure Proxy 6.0.3 allows remote authenticated users to cause XSS, cache poisoning, or session hijacking. The request-handling path improperly validates attacker-controlled Host header input; IBM has not identified a narrower file or function. Exploitation requires low privileges and user interaction, and the reported effects are limited to confidentiality and integrity.
The record
- CVE
- CVE-2022-34362
- Published
- Feb 8, 2023
- Updated
- Mar 24, 2025
- Vendor
- IBM
- Product
- IBM Sterling Secure Proxy
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 8, 2023CVE publishedPublication date reported by the CVE source.
- Mar 24, 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=6.0.3
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