Link poisoning via unvalidated Host header
Published Oct 30, 2025 · Updated Oct 30, 2025
Host header injection in Nagios XI before 2024R1.2.2 allows remote attackers to poison generated links and responses through HTTP requests. The URL-construction logic accepts the untrusted HTTP Host header as an authoritative origin when producing absolute URLs, without sufficient validation. No authentication is required; poisoned links or responses can support credential phishing, account-recovery link hijacking, or web-cache poisoning.
Summary
What happened
Host header injection in Nagios XI before 2024R1.2.2 allows remote attackers to poison generated links and responses through HTTP requests. The URL-construction logic accepts the untrusted HTTP Host header as an authoritative origin when producing absolute URLs, without sufficient validation. No authentication is required; poisoned links or responses can support credential phishing, account-recovery link hijacking, or web-cache poisoning.
The record
- CVE
- CVE-2024-14006
- Published
- Oct 30, 2025
- Updated
- Oct 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-346, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 30, 2025CVE publishedPublication date reported by the CVE source.
- Oct 30, 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?
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.
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