Security Resilience

CVE-2023-7322

Access Control in Nagios Log Server ≤ 2024

Public PoCAccess Control
Published
30 October 2025
Modified
06 November 2025
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.011 64th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-7322 is a high-severity Incorrect Authorization (CWE-863) vulnerability in Nagios Log Server. Its CVSS base score is 8.7 (High).

Operationally, ranked in the top 36% 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-24 (Access Control Decisions) and AC-25 (Reference Monitor) — 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-2023-7322 is an incorrect authorization vulnerability (CWE-863) in Nagios Log Server versions prior to 2024R1. The flaw stems from inadequate checks that allow users without required API permissions to invoke API endpoints anyway, enabling unintended access to data and execution of actions exposed through the API. This permits authenticated but non-privileged users to read or modify resources beyond their designated rights.

The vulnerability can be exploited by an authenticated attacker with low privileges over the network, requiring low attack complexity and no user interaction. Successful exploitation grants high confidentiality and integrity impacts, such as unauthorized data access or modification, with no availability disruption. The CVSS v3.1 base score is 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Advisories from Nagios and Vulncheck recommend upgrading to Nagios Log Server 2024R1 to address the authorization flaw, as detailed in the official changelog and the Vulncheck advisory on the incorrect authorization granting full API access.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Nagios Log Server versions prior to 2024R1 contain an incorrect authorization vulnerability. Users who lacked the required API permission were nevertheless able to invoke API endpoints, resulting in unintended access to data and actions exposed via the API. This incorrect…

more

authorization check could allow authenticated but non-privileged users to read or modify resources beyond their intended rights.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-34273Same product: Nagios Log Server
CVE-2025-44824Same product: Nagios Log Server
CVE-2025-34323Same product: Nagios Log Server
CVE-2025-34270Same product: Nagios Log Server
CVE-2023-7323Same product: Nagios Log Server
CVE-2025-29471Same product: Nagios Log Server
CVE-2025-34274Same product: Nagios Log Server
CVE-2025-34271Same product: Nagios Log Server
CVE-2025-34277Same product: Nagios Log Server
CVE-2025-44823Same product: Nagios Log Server

Affected Assets

nagios
log server
≤ 2024

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.

AC-24 ensures access-control decisions are made and applied consistently, reducing the chance of an incorrect authorization result.

A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.

Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.

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.

blocks

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

blocks

A.5.18's provisioning, revocation, review and adjustment of access rights (incl. before role changes/termination, with segregation and owner approval) directly stops incorrect authorization decisions from being exploitable in the vast majority of cases; the bounded remainder is incorrectness inside the authorization logic itself (e.g. flawed conditional or missing check) rather than rights that were wrongly granted.

blocks

A.8.3 directly mandates restricting access to information per policies via configuration, identity/group controls, isolation, and dynamic techniques that enforce correct authorization decisions, addressing most but not all slices of CWE-863 (e.g., remainder in non-access-decision authorization errors like timing or environmental factors).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-863, a class-level weakness, and none of its children carries one either.

References