dbcve.org
Nagios XiApplication · Nagios

CVE-2024-13999

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Nagios XI versions prior to 2024R1.1.3, under certain circumstances, disclose the server's Active Directory (AD) or LDAP authentication token to an authenticated user. Exposure of the server’s AD/LDAP token could allow domain-wide authentication misuse, escalation of privileges, or further compromise of network-integrated systems.

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 confidence

Nagios XI versions prior to 2024R1.1.3 contain an information disclosure vulnerability where the server's Active Directory or LDAP authentication token is exposed to authenticated users under certain circumstances. This token exposure allows attackers to potentially perform domain-wide authentication misuse, privilege escalation, and further compromise network-integrated systems.

MitigationUpgrade to Nagios XI 2024R1.1.3 or later to remediate the token disclosure. If upgrading is not immediately feasible, consider reviewing LDAP/AD integration settings and limiting administrative access until the patch can be applied.

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
Nagios XiApplication
Affected:< 2024= 2024

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nagios XI version
    Log into the Nagios XI web interface and navigate to Admin > System Information, or run 'cat /usr/local/nagiosxi/etc/xi-sys.cfg' from the server command line to find the installed version number
    Affected if The version is earlier than 2024R1.1.3 or shows '2024' without the 1.3 patch level
  2. Confirm LDAP or Active Directory integration is enabled
    In the Nagios XI web interface, go to Admin > LDAP/AD Configuration or check the /usr/local/nagiosxi/etc/components/ldap_ad_integration.php configuration file for active authentication settings
    Affected if LDAP or Active Directory authentication is configured and active on the Nagios XI server
  3. Verify if the LDAP/AD bind credentials include a token
    Review the LDAP/AD configuration section in Admin > LDAP/AD Settings to identify if a service account password or bind token is stored as part of the integration
    Affected if A bind account with domain authentication credentials is configured, which would be the token subject to exposure

The environment is likely affected if Nagios XI version is prior to 2024R1.1.3 and LDAP/Active Directory authentication is configured, as the stored authentication token could be exposed to any authenticated user with access to the relevant interface area.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2024 or later
Fixed in 2024
Interim mitigation

Upgrade to Nagios XI 2024R1.1.3 or later to remediate the token disclosure. If upgrading is not immediately feasible, consider reviewing LDAP/AD integration settings and limiting administrative access until the patch can be applied.

Recommended fix Moderate confidence

2024R1.1.3

  1. 1. Back up the current Nagios XI installation and database before attempting any upgrade.
  2. 2. Log in to the Nagios XI server as root via SSH or console.
  3. 3. Navigate to the Nagios XI admin interface and check the current version under 'Admin' > 'System Information'.
  4. 4. Run the official Nagios XI update command: ./upgrade xi or use the web-based update mechanism under 'Admin' > 'System Extensions' > 'Check for Updates'.
  5. 5. If prompted, select the option to upgrade to the latest stable release (2024R1.1.3 or later).
  6. 6. Wait for the upgrade to complete and ensure all services restart properly.
  7. 7. Verify the upgrade was successful by checking the version number in the admin interface.
  8. 8. Test that AD/LDAP authentication still functions correctly after the upgrade.
Caveat Review Nagios XI 2024R1.1 release notes for any new features or configuration changes that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13999 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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