HTTP Host-header poisoning
Published Jul 25, 2023 · Updated Oct 24, 2024
Host-header poisoning in RTX TRAP 1.0 allows remote attackers to influence application output with a crafted HTTP Host header. The public record does not identify the affected route, function, or exact operation that consumes the untrusted header. Remote access requires no account, but a victim must interact with the poisoned output; no service interruption is reported.
Summary
What happened
Host-header poisoning in RTX TRAP 1.0 allows remote attackers to influence application output with a crafted HTTP Host header. The public record does not identify the affected route, function, or exact operation that consumes the untrusted header. Remote access requires no account, but a victim must interact with the poisoned output; no service interruption is reported.
The record
- CVE
- CVE-2022-31458
- Published
- Jul 25, 2023
- Updated
- Oct 24, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-116, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2023CVE publishedPublication date reported by the CVE source.
- Oct 24, 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.
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
- Rohit Gautam host-header poisoning proof of conceptproof of concept · unverified
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