dbcve.org
Log ServerApplication · Nagios

CVE-2025-34271

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 Log Server versions prior to 2024R2.0.2 contain a vulnerability in the cluster manager component when requesting sensitive credentials from peer nodes over an unencrypted channel even when SSL/TLS is enabled in the product configuration. As a result, an attacker positioned on the network path can intercept credentials in transit. Captured credentials could allow the attacker to authenticate as a cluster node or service account, enabling further unauthorized access, lateral movement, or system compromise.

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 Log Server versions prior to 2024R2.0.2 have a vulnerability in the cluster manager component where sensitive credentials are requested from peer nodes over an unencrypted channel, even when SSL/TLS is enabled in the product configuration. A network-positioned attacker can intercept these credentials in transit and use them to authenticate as a cluster node or service account.

MitigationUpgrade to Nagios Log Server 2024R2.0.2 or later to remediate the vulnerability. Additionally, implement network segmentation and monitor for suspicious inter-node traffic to reduce risk during the remediation window.

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
Log ServerApplication
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 installed Nagios Log Server version
    Access the Nagios Log Server web interface and navigate to the About or System Information page to view the exact version number. Alternatively, check the version via command line using 'nls --version' or by inspecting the installed package version with your system's package manager.
    Affected if The version is prior to 2024R2.0.2 or shows only '2024' without the 2024R2.0.2 patch level.
  2. Verify if clustering is enabled
    Check the Nagios Log Server web interface under the Cluster or Nodes configuration section to determine if the cluster manager component is active. Alternatively, inspect the cluster configuration files in the Nagios Log Server data directory for node definitions.
    Affected if Clustering is enabled and the server is configured as part of a multi-node cluster.
  3. Check SSL/TLS configuration status
    Navigate to the SSL/TLS settings in the Nagios Log Server web interface or inspect the configuration files to determine whether SSL/TLS encryption is enabled for inter-node communications.
    Affected if SSL/TLS is configured in any state (enabled or disabled) because the vulnerability affects the credential request channel regardless of this setting.
  4. Inspect cluster communication ports
    Use netstat or ss commands to list open ports and identify those associated with Nagios Log Server cluster communications. Compare the listening ports against expected cluster port configurations.
    Affected if Cluster ports are open and accepting connections without explicit encryption wrapping at the application layer.

You are affected if your Nagios Log Server version is 2024 or any version prior to 2024R2.0.2 AND the cluster manager component is enabled, regardless of SSL/TLS configuration.

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 Log Server 2024R2.0.2 or later to remediate the vulnerability. Additionally, implement network segmentation and monitor for suspicious inter-node traffic to reduce risk during the remediation window.

Recommended fix High confidence

2024R2.0.2 or later

  1. Back up the current Nagios Log Server configuration and data directory before proceeding with the upgrade
  2. Download Nagios Log Server version 2024R2.0.2 or later from the official Nagios download page
  3. Stop the Nagios Log Server services on all cluster nodes
  4. Follow the official Nagios upgrade documentation for your installation method (ZIP/tarball or RPM/DEB package)
  5. Install the new version on all cluster nodes, preserving configuration files
  6. Start the Nagios Log Server services on all cluster nodes
  7. Log in to the web interface and navigate to the cluster manager settings
  8. Verify that SSL/TLS is properly enabled and the credential transmission issue is resolved
Caveat Review Nagios release notes for 2024R2.0.2 for any configuration or feature changes that may require adjustment

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

Fix this in Log Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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