CVE-2024-14006
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNagios XI versions prior to 2024R1.2.2 contain a host header injection vulnerability. The application trusts the user-supplied HTTP Host header when constructing absolute URLs without sufficient validation. An unauthenticated, remote attacker can supply a crafted Host header to poison generated links or responses, which may facilitate phishing of credentials, account recovery link hijacking, and web cache poisoning.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNagios XI prior to 2024R1.2.2 contains a host header injection vulnerability where the application trusts the user-supplied HTTP Host header when constructing absolute URLs without sufficient validation. An unauthenticated remote attacker can supply a crafted Host header to poison generated links or responses, facilitating phishing, account recovery link hijacking, and web cache poisoning.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2024= 2024CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Nagios XI is installedLook for Nagios XI installation directories such as /usr/local/nagiosxi/ or check for the nagiosxi web application path. Alternatively, check running web server processes for nagiosxi.Affected if Nagios XI is not found on the system - the CVE does not apply.
-
Determine the installed Nagios XI versionCheck the version file at /usr/local/nagiosxi/etc/version.ini, or access the Nagios XI admin interface and navigate to the About or System Information page to view the version number.Affected if The installed version is prior to 2024R1.2.2 (including any 2024.x version before 2024R1.2.2).
-
Confirm the version matches the affected rangeCompare the discovered version number against the affected range: versions prior to 2024, or version 2024.x versions before 2024R1.2.2. Versions 2024R1.2.2 and later are NOT affected.Affected if The version number is in the range < 2024 or = 2024 (any 2024.x release before 2024R1.2.2).
-
Check if the web application is accessibleAttempt to access the Nagios XI web interface via HTTP/HTTPS to confirm the application is running and reachable.Affected if The application is accessible externally and uses the affected version - the host header injection could be exploited by remote attackers.
If Nagios XI is installed and the version is prior to 2024R1.2.2 (including any 2024.x release before 2024R1.2.2), the environment is affected by this host header injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2024
Upgrade to Nagios XI 2024R1.2.2 or later, or implement server-side validation of the Host header using an allowlist of permitted hostnames to prevent manipulation of generated URLs.
2024R1.2.2
- Download Nagios XI version 2024R1.2.2 or later from the official Nagios website
- Follow the standard Nagios XI upgrade procedure documented in the admin guide
- Verify the upgrade was successful by logging into the Nagios XI web interface
- Confirm the version displayed shows 2024R1.2.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-14006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-14006 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data