Nagios Log Server
CVE-2025-34270
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain admin access to Log Server UI
-
DeliveryPerform or view AD/LDAP user import
-
ExploitPassword rendered in plaintext in UI/logs
-
ExecutionHarvest exposed directory credentials
-
ImpactReuse credentials for lateral movement
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V14 - Data Protection Encrypted storage of sensitive data
|
| Exploitation Conditions | Exploitation requires the AD/LDAP user-import feature to be used, and an actor must hold administrator-level access to the Nagios Log Server interface, its logs, or diagnostic output where import results are displayed (PR:H). The limiting factors are significant: this is not remotely exploitable by an unauthenticated attacker, no victim user interaction by a third party is needed, and exposure only occurs on versions prior to 2024R2.0.2 where the password field is not obfuscated. The concrete prerequisite is organizational use of AD/LDAP account import; environments that do not import directory users via this feature are not exposed. |
| Impact | This is a moderate, authentication-gated information-disclosure flaw (CWE-312, cleartext handling of sensitive data), not an urgent internet-facing threat. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N) scores 6.9 and is internally consistent with the description: exploitation yields high confidentiality impact (leaked plaintext credentials) but no integrity or availability impact, and it requires high privileges (PR:H) - i.e., an administrator performing or viewing an AD/LDAP user import. EPSS is low at 0.63% (48th percentile), the CVE is NOT on CISA KEV, and no public exploit code is referenced, so there is no public exploit identified at time of analysis. The signals are coherent rather than conflicting: a low EPSS, absence of KEV, and a PR:H requirement all point to a low-likelihood, admin-dependent exposure rather than mass exploitation. The real risk is contextual - the leaked password may belong to a privileged directory account whose exposure could enable lateral movement, and the 'automatable' potential is low because an attacker must already hold admin access to the Log Server UI/logs. No SSVC decision data was provided in the input, so exploitation-status/automatable/technical-impact cannot be sourced from a vendor SSVC record and are inferred only from CVSS. Treat as a standard-priority patch item, not an emergency. |
| Exploit ScenarioDerived | A Nagios Log Server administrator configures AD/LDAP user import; because the password field is not obfuscated, the plaintext credential supplied for the imported account is rendered in the import-results UI, written to logs, or surfaced in diagnostic output. Any administrator or operator with access to that interface or those logs - or an attacker who has already compromised an admin-level account - can read the exposed directory credential. No public exploit code is referenced; exploitation requires existing privileged access (PR:H) rather than remote unauthenticated interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Nagios Log Server versions prior to 2024R2.0.2 handle AD/LDAP user-import credentials in cleartext, printing the plaintext password into the user interface, import results, logs, or diagnostic output where administrators can read it. The exposure is gated behind high-privilege access (CVSS 3.1 PR:H) and only occurs when the AD/LDAP account-import feature is actually used, so organizations that never import directory users through this workflow are not affected. EPSS is low at 0.63% (48th percentile) and no public exploit code has been identified at time of analysis; this is a moderate, authentication-gated information-disclosure flaw rather than an urgent internet-facing threat, and no KEV entry exists.
RemediationAI
Apply the vendor-released patch: upgrade Nagios Log Server to 2024R2.0.2 or later, which obfuscates the password field during AD/LDAP imports; see https://www.nagios.com/products/security/#log-server-2024R2 and https://www.nagios.com/changelog/#log-server for the release details. Until upgrading, avoid performing AD/LDAP user imports on affected builds and treat any password previously entered through this feature as compromised: rotate the directory bind/import account credentials immediately and update the stored configuration, understanding that the old credential remains valid until rotated and that rotation will interrupt LDAP binds until the new value is in place. Restrict administrative access to the Nagios Log Server UI, log files, and support/diagnostic bundle output to the smallest possible set of trusted accounts, since the leak is only reachable by PR:H-level users. Where password reuse exists, rotate matching credentials elsewhere. Review and purge captured diagnostic bundles and log archives that may already contain cleartext values, and configure log retention/forwarding so import-related output is not broadly distributed; note that forwarding to a SIEM widens the exposure surface rather than containing it.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a CWE-312 cleartext storage/handling defect in Nagios Log Server's AD/LDAP user-import subsystem. When an administrator supplies a password for an imported directory account, the application fails to obfuscate or mask that field before persisting or rendering it, so the plaintext value can surface in the administrative UI, the import result view, log files, and diagnostic bundles generated by the product. The underlying technology is directory-integration (Active Directory / LDAP bind) used to sync users into the Nagios Log Server authentication store; the security boundary that matters is who can view those screens, logs, and diagnostics. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) agree that confidentiality is the only impacted property, with prerequisite high privilege and no integrity or availability impact. CPE data enumerates the affected line as Nagios Log Server 2024 R1 through R1.3.3 plus earlier releases, with 2024R2.0.2 as the first fixed build.
Know when Nagios gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Admin access to perform/view the import is required so PR:H; reachable over the web UI (AV:N, AC:L); plaintext credential leak gives C:H with no integrity or availability impact.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
Nagios Log Server versions prior to 2024R2.0.2 contain a vulnerability in the AD/LDAP user import functionality as it fails to obfuscate the password field during import. As a result, the plaintext password supplied for imported accounts may be exposed in the user interface, logs, or other diagnostic output. This can leak sensitive credentials to administrators or anyone with access to import results.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Multiple stack-based buffer overflows in the get_history function in history.cgi in Nagios Core before 3.4.4, and Icinga
Incomplete blacklist vulnerability in nrpc.c in Nagios Remote Plug-In Executor (NRPE) before 2.14 might allow remote att
Nagios XI version xi-5.7.5 is affected by cross-site scripting (XSS). Rated medium severity (CVSS 6.1), this vulnerabili
Multiple off-by-one errors in Nagios Core 3.5.1, 4.0.2, and earlier, and Icinga before 1.8.5, 1.9 before 1.9.4, and 1.10
MagpieRSS, as used in the front-end component in Nagios Core before 4.2.2 might allow remote attackers to read or write
Snoopy 1.0 in Nagios XI 5.5.6 allows remote unauthenticated attackers to execute arbitrary commands via a crafted HTTP r
SQL injection vulnerability in the core config manager in Nagios XI 5.2.x through 5.4.x before 5.4.13 allows an attacker
Authentication bypass vulnerability in the core config manager in Nagios XI 5.2.x through 5.4.x before 5.4.13 allows an
A path traversal vulnerability exists in Nagios XI below version 5.8.5 AutoDiscovery component and could lead to post au
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB