CVE-2024-13995
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.1.2 may (confirmed in 2024R1.1 and 2024R1.1.1) disclose sensitive user account information (including API keys and hashed passwords) to authenticated users who should not have access to that data. Exposure of API keys or password hashes could lead to account compromise, abuse of API privileges, or offline cracking attempts.
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 versions prior to 2024R1.1.2 contain an improper access control vulnerability allowing authenticated users to view sensitive account information (API keys and password hashes) belonging to other users who should not be accessible to them.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Nagios XI versionNavigate to Admin > System Info in the XI web interface, or run 'cat /usr/local/nagiosxi/var/xi-sys.cfg' from the command line to retrieve the exact version number.Affected if The version is prior to 2024R1.1.2 or shows '2024' without the 1.2 patch level.
-
Confirm user accounts existNavigate to Admin > Users or query the database (e.g., 'SELECT * FROM xi_users' in the nagiosql or nagiosxi database) to verify multiple authenticated users are configured.Affected if Two or more user accounts exist in the system, creating the condition where user-to-user information disclosure is possible.
-
Examine API key exposure potentialAs an authenticated user, navigate to the user profile or API key management section in the web interface, or inspect the xi_users table for the api_key column.Affected if API keys are stored in plaintext or retrievable through user enumeration, indicating the vulnerability is exploitable.
-
Review password hash accessibilityQuery the user authentication database (e.g., 'SELECT user_name, password FROM xi_users' or similar) to check if password hashes for other users are visible to non-admin accounts.Affected if Authenticated non-admin users can query or view password hash fields belonging to other users.
-
Check for unusual API or user info requests in logsReview /usr/local/nagiosxi/var/nagios.log or the Apache access log for requests to user information endpoints that may indicate exploitation (e.g., repeated queries to userprofile or API key retrieval endpoints).
You are affected if your Nagios XI version is below 2024R1.1.2 and multiple user accounts exist, allowing any authenticated user to access sensitive credentials of other users through the application.
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 Nagios XI to version 2024R1.1.2 or later. Additionally, rotate any exposed API keys and consider resetting passwords for affected accounts as a precautionary measure.
2024R1.1.2 or later
- Backup your current Nagios XI installation and database before proceeding with any upgrade
- Identify your current Nagios XI version by navigating to Admin > System Information in the XI interface
- Download Nagios XI version 2024R1.1.2 or later from the official Nagios website (www.nagios.com)
- Follow the standard Nagios XI upgrade procedure: run the upgrade script or use the web-based upgrade interface
- After upgrade completion, verify the new version is installed: Admin > System Information > should show 2024R1.1.2 or later
- Test that the vulnerability is remediated by confirming unauthorized users cannot access sensitive account data (API keys, password hashes)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13995 — 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-13995 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