Unauthenticated redirects via trusted Host header
Published Aug 22, 2021 · Updated Aug 4, 2024
Host header injection in Canon Oce Print Exec Workgroup 1.3.2 allows remote attackers to redirect web-interface responses. PEWGStartServlet trusts an unvalidated Host header when constructing the HTTP 302 Location header and an HTML link. No authentication is required; a crafted request can direct a client to an attacker-controlled domain, but the proof demonstrates neither data disclosure nor code execution.
Summary
What happened
Host header injection in Canon Oce Print Exec Workgroup 1.3.2 allows remote attackers to redirect web-interface responses. PEWGStartServlet trusts an unvalidated Host header when constructing the HTTP 302 Location header and an HTML link. No authentication is required; a crafted request can direct a client to an attacker-controlled domain, but the proof demonstrates neither data disclosure nor code execution.
The record
- CVE
- CVE-2021-39367
- Published
- Aug 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-116
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- IthacaLabs Host Header Injection proofproof of concept · demonstrated
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