dbcve.org
Log ServerApplication · Nagios

CVE-2024-58273

HIGH · 7.8 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
80/100
Remediation priority · High
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 2024R1.0.2 contain a local privilege escalation vulnerability that allows an attacker who could execute commands as the Apache web user (or the backend shell user) to escalate to root on the host.

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 2024R1.0.2 contain a local privilege escalation vulnerability where an attacker with command execution capability as the Apache web user or backend shell user can gain root privileges on the host.

MitigationUpgrade Nagios Log Server to version 2024R1.0.2 or later to remediate this vulnerability.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nagios Log Server installation
    Look for Nagios Log Server processes or directories. Common paths include /usr/local/nagioslogserver, /opt/nagioslogserver, or check running processes with 'ps aux | grep -i nagios'. Also check for RPM packages with 'rpm -qa | grep -i nagioslogserver' or DEB packages with 'dpkg -l | grep -i nagioslogserver'.
    Affected if Nagios Log Server is installed and running on the system.
  2. Determine installed version
    Check the installed version by examining version files in the installation directory, such as 'cat /usr/local/nagioslogserver/nagioslogserver/version.txt' or running 'nagioslogserver --version' if available. Compare your version against the affected range: versions prior to 2024R1.0.2, or version 2024.
    Affected if The installed version is 2024 or any version earlier than 2024R1.0.2.
  3. Verify Apache service user context
    Check which user the Apache service runs as by running 'ps aux | grep httpd' or 'ps aux | grep apache2' depending on your OS. The vulnerability requires command execution capability as the Apache web user to exploit the privilege escalation.
    Affected if Apache is running as a low-privilege user (such as apache, www-data, or nagios) and the Nagios Log Server version is affected.
  4. Check for backend shell access
    Review system access to determine if any backend shell accounts exist. The vulnerability also affects attackers with backend shell user access. Check for system accounts with shell access using 'grep -E '^(nagios|apache|www-data):' /etc/passwd'.
    Affected if Backend shell accounts exist on the system alongside an affected Nagios Log Server version.

A system is affected if Nagios Log Server version 2024 or any version prior to 2024R1.0.2 is installed AND the Apache service is running as a user with limited privileges, or if backend shell user accounts exist on the host.

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 Log Server to version 2024R1.0.2 or later to remediate this vulnerability.

Recommended fix High confidence

2024R1.0.2

  1. Backup the current Nagios Log Server installation and configuration data
  2. Download Nagios Log Server version 2024R1.0.2 or later from the official Nagios website (www.nagios.com)
  3. Stop the Nagios Log Server services before proceeding with the upgrade
  4. Follow the official upgrade documentation for Nagios Log Server to apply the update
  5. Verify the upgrade was successful by checking the version number in the web interface
  6. Restart the Nagios Log Server services
  7. Confirm the services are running properly and the web interface is accessible

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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