Cache poisoning via improper Host header validation
Published Aug 17, 2021 · Updated Sep 16, 2024
HTTP Host header injection in IBM API Connect 5.0.0.0 through 5.0.8.10 allows remote authenticated users to poison caches or hijack sessions. Host-header processing fails to validate the attacker-supplied hostname, but IBM has not identified the responsible handler or disclosed its downstream use. Low-privilege authentication is required, and resulting response manipulation enables cross-site scripting, cache poisoning, or session hijacking.
Summary
What happened
HTTP Host header injection in IBM API Connect 5.0.0.0 through 5.0.8.10 allows remote authenticated users to poison caches or hijack sessions. Host-header processing fails to validate the attacker-supplied hostname, but IBM has not identified the responsible handler or disclosed its downstream use. Low-privilege authentication is required, and resulting response manipulation enables cross-site scripting, cache poisoning, or session hijacking.
The record
- CVE
- CVE-2020-4706
- Published
- Aug 17, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- API Connect
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 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=5.0.0.0
- Affected versionversion=5.0.8.10
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