dbcve.org
Nagios XiApplication · Nagios

CVE-2024-14003

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.2 are vulnerable to remote code execution (RCE) through its NRDP (Nagios Remote Data Processor) server plugins. Insufficient validation of inbound NRDP request parameters allows crafted input to reach command execution paths, enabling attackers to execute arbitrary commands on the underlying host in the context of the web/Nagios service.

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 · moderate confidence

Nagios XI versions prior to 2024R1.2 contain a critical input validation flaw in the NRDP (Nagios Remote Data Processor) server plugins. Attackers can send specially crafted NRDP requests with malicious parameters that bypass insufficient validation checks, allowing arbitrary OS command execution in the context of the web service.

MitigationUpgrade Nagios XI to version 2024R1.2 or later to obtain the vendor patch. As an interim control, restrict network access to NRDP endpoints and implement strict input validation at a network perimeter device.

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. Confirm Nagios XI is installed
    Locate Nagios XI installation directories, common paths include /usr/local/nagiosxi, /opt/nagiosxi, or check system packages/services for nagiosxi
    Affected if Nagios XI software is present on the system
  2. Identify installed Nagios XI version
    Run command to check version, typically found in Nagios XI admin interface under 'System Profile' or via command line like 'cat /usr/local/nagiosxi/etc/version.ini' or similar version file
    Affected if Version is prior to 2024R1.2 or shows only year 2024 without R1.2 suffix
  3. Determine if NRDP is enabled
    Check Nagios XI configuration for NRDP server settings, typically in /usr/local/nagiosxi/etc/nrdp.cfg or through the Nagios XI web interface under 'Config' > 'NRDP'
    Affected if NRDP is enabled and accessible on the network
  4. Review NRDP access logs for suspicious requests
    Examine NRDP server logs, typically in /usr/local/nagiosxi/var/log/nrdp.log or similar, for unusual parameter patterns or unexpected remote hosts
    Affected if Logs contain unexpected or malformed NRDP requests with unusual parameter values
  5. Check for unauthorized command execution artifacts
    Review web service logs and system process history for commands originating from NRDP handlers that are unexpected or were not initiated by legitimate admin actions
    Affected if Evidence of arbitrary commands executed via NRDP that were not part of intended monitoring workflows

You are affected if Nagios XI version is prior to 2024R1.2 AND NRDP server is enabled, as the vulnerability requires the NRDP component to be present for exploitation.

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 Nagios XI to version 2024R1.2 or later to obtain the vendor patch. As an interim control, restrict network access to NRDP endpoints and implement strict input validation at a network perimeter device.

Recommended fix High confidence

Nagios XI 2024R1.2 or later

  1. 1. Backup your Nagios XI installation and database before proceeding with any upgrade.
  2. 2. Check the current Nagios XI version by navigating to Admin > System Information in the web UI or running: getversion
  3. 3. Download the latest Nagios XI 2024R1.2 or later version from the official Nagios website (www.nagios.com).
  4. 4. Apply the upgrade by running the installer as root: ./fullinstall
  5. 5. After upgrade completes, restart services: systemctl restart nagios xi-httpd
  6. 6. Verify the upgrade was successful and the version shows 2024R1.2 or later.
  7. 7. Test that NRDP functionality works correctly with the fix in place.

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-14003 — 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-14003 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