CVE-2025-44823
Nagios Log Server ≤ 2024
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-44823 is a critical-severity Exposure of Sensitive System Information to an Unauthorized Control Sphere (CWE-497) vulnerability in Nagios Log Server. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique System Information Discovery (T1082); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-44823 is a critical vulnerability in Nagios Log Server versions prior to 2024R1.3.2, stemming from improper restriction of knowledge to authenticated users (CWE-497). It allows any authenticated user to retrieve cleartext administrative API keys through an unauthenticated API endpoint at /nagioslogserver/index.php/api/system/get_users. The issue, tracked internally as GL:NLS#475, carries a CVSS v3.1 base score of 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), highlighting its severe potential impact across confidentiality, integrity, and availability with a changed scope.
An attacker with low-privilege authenticated access, such as a standard user account, can exploit this remotely over the network with minimal complexity and no user interaction required. Successful exploitation exposes sensitive administrative API keys in plaintext, enabling privilege escalation to full administrative control. This could allow attackers to manipulate server configurations, access logs, execute arbitrary actions via the API, or pivot to further compromise the environment.
Advisories reference a proof-of-concept exploit available on Exploit-DB (ID 52177) and point to the Nagios changelog for patch details. Mitigation involves upgrading to Nagios Log Server 2024R1.3.2 or later, which addresses the flaw by restricting access to administrative data in the affected API call.
Public availability of an Exploit-DB entry indicates active interest from the security research community, though no widespread real-world exploitation has been reported as of the CVE publication on 2025-10-07.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-31897
Vulnerability Data
Nagios Log Server before 2024R1.3.2 allows authenticated users to retrieve cleartext administrative API keys via a /nagioslogserver/index.php/api/system/get_users call. This is GL:NLS#475.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 4 OS baselines
V14.1.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations for logical access, directly stopping unauthorized actors from reaching sensitive system information.
Enforces information flow policies that block sensitive system data from crossing into unauthorized control spheres.
Limits privileges so that only the minimum necessary access is granted, reducing the chance of exposing system-level details.
Controls communications at external and key internal boundaries to keep sensitive system information inside authorized spheres.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege access permissions directly prevents unauthorized actors from reaching sensitive system information.
Protecting environments from unauthorized logical access stops exposure of internal system details to outsiders.
Secure-development practices reduce the chance of code paths that leak sensitive system information.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Keeping internal maps, directories, and signage from public view prevents disclosure of system or facility details that could aid reconnaissance or targeted attacks.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. prevents CWE-497
- V-248580 OL 8 must prevent kernel profiling by unprivileged users. prevents CWE-497
RHEL 8 (1 rule)
- V-230270 RHEL 8 must prevent kernel profiling by unprivileged users. prevents CWE-497
Ubuntu 22.04 (1 rule)
- V-260470 Ubuntu 22.04 LTS, when booted, must require authentication upon booting into single-user and maintenance modes. prevents CWE-497
Ubuntu 24.04 (1 rule)
- V-270675 Ubuntu 24.04 LTS when booted must require authentication upon booting into single-user and maintenance modes. prevents CWE-497