Monitoring suppression via read-only downtime scheduling
Published Jun 29, 2022 · Updated Aug 3, 2024
Incorrect authorization in Nagios XI 5.8.5 and earlier allows remote authenticated users to disable monitoring through scheduled downtime. The downtime.php handler accepts crafted POST requests from read-only accounts because its permission check does not enforce downtime-scheduling rights. Read-only Nagios access is sufficient to schedule downtime for any host or service, suppressing all monitoring checks indefinitely.
Summary
What happened
Incorrect authorization in Nagios XI 5.8.5 and earlier allows remote authenticated users to disable monitoring through scheduled downtime. The downtime.php handler accepts crafted POST requests from read-only accounts because its permission check does not enforce downtime-scheduling rights. Read-only Nagios access is sufficient to schedule downtime for any host or service, suppressing all monitoring checks indefinitely.
The record
- CVE
- CVE-2022-29271
- Published
- Jun 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 29, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo