CVE-2025-34270VulnerabilityPublished 30 Oct 2025Updated 17 Nov 2025

CVE-2025-34270: Nagios Log Server · Cleartext Storage of Sensitive Information

Affects Nagios Log ServerSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Nagios Log Server	Affected =0	Fixed in–

AI-suggested

1. Upgrade Nagios Log Server to version 2024R2.0.2 or later once the patch is released to ensure the password obfuscation issue is resolved. 2. Until a patch is available, restrict access to the AD/LDAP user import functionality and the associated logs and UI screens to only the most trusted administrators. 3. Implement strict role-based access controls (RBAC) to limit who can view import results and diagnostic outputs containing sensitive information. 4. Regularly audit access logs to detect any unauthorized access to import results or logs. 5. Avoid using shared or generic accounts for AD/LDAP imports to reduce the risk of credential exposure. 6. Consider encrypting or masking sensitive fields in custom monitoring or logging configurations if possible. 7. Educate administrators about the risk of credential exposure through logs and UI and enforce secure operational procedures. 8. Monitor Nagios vendor advisories for updates and apply patches promptly. 9. If feasible, isolate Nagios Log Server in a secure network segment to limit exposure. 10. Review and harden logging and diagnostic configurations to minimize sensitive data exposure.

Description

CVE-2025-34270 is a medium severity vulnerability in Nagios Log Server versions prior to 2024R2.0.2 affecting the AD/LDAP user import functionality. The flaw causes plaintext passwords supplied during user import to be stored or displayed without obfuscation, exposing sensitive credentials in the user interface, logs, or diagnostic outputs. This exposure risks credential leakage to administrators or any users with access to these outputs. The vulnerability requires privileged access to exploit and does not need user interaction. Although no exploits are currently known in the wild, the vulnerability could facilitate unauthorized access if exposed. Organizations using affected Nagios Log Server versions should update promptly and restrict access to import results and logs. European organizations with deployments of Nagios Log Server, especially in critical infrastructure or large enterprises, are at risk. Countries with significant Nagios usage and strong regulatory environments around data protection should prioritize mitigation.

Impact

For European organizations, the exposure of plaintext passwords in Nagios Log Server can lead to unauthorized access if these credentials are intercepted or accessed by malicious insiders or attackers who have gained privileged access. This risk is particularly acute in sectors with stringent data protection requirements such as finance, healthcare, and critical infrastructure, where Nagios Log Server is often used for monitoring and logging. Credential leakage can facilitate lateral movement within networks, privilege escalation, and compromise of other connected systems. Additionally, exposure of sensitive credentials may lead to violations of GDPR and other data protection regulations, resulting in legal and financial penalties. The impact is compounded in environments where audit logs and diagnostic outputs are widely accessible or insufficiently protected. Organizations relying on Nagios Log Server for centralized log management and monitoring must consider the risk of credential exposure as a vector for broader security breaches.

Summary

CVE-2025-34270 is a vulnerability identified in Nagios Log Server versions prior to 2024R2.0.2, specifically in the Active Directory (AD) and Lightweight Directory Access Protocol (LDAP) user import functionality. The issue arises because the system fails to obfuscate or encrypt the password field when importing user accounts from AD/LDAP. As a result, the plaintext passwords provided during import can be exposed in multiple locations, including the user interface where import results are displayed, system logs, and other diagnostic outputs. This cleartext storage and display of sensitive credentials violate secure coding practices and correspond to CWE-312 (Cleartext Storage of Sensitive Information) and CWE-522 (Insufficiently Protected Credentials). The vulnerability requires an attacker to have privileged access (high privileges) to the Nagios Log Server environment to trigger the import process or view the import results, and no user interaction is necessary. The CVSS v4.0 base score is 6.9, indicating a medium severity level, with network attack vector, low attack complexity, and no privileges required for network access but requiring high privileges on the system itself. The vulnerability does not affect confidentiality, integrity, or availability of the system beyond credential exposure but can lead to credential compromise if logs or UI access is not properly restricted. No public exploits have been reported yet, but the risk remains significant due to the sensitive nature of the exposed data. Nagios has not yet released a patch as of the publication date, so mitigation relies on access controls and operational security measures.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 22:18 UTC

WeaknessesCWE-312, CWE-522

Technical details

References

Community reviews

Related threats