CVE-2022-29271
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 · uneditedIn Nagios XI through 5.8.5, a read-only Nagios user (due to an incorrect permission check) is able to schedule downtime for any host/services. This allows an attacker to permanently disable all monitoring checks.
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 confidenceNagios XI through version 5.8.5 contains an incorrect permission check that allows read-only users to schedule downtime on any host or service. This authorization flaw enables a low-privilege user to bypass intended role-based access controls and disable all monitoring checks by scheduling permanent downtime.
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<= 5.8.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Determine Nagios XI versionAccess the Nagios XI web interface or command line to retrieve the installed version number. Compare it to the affected range: version 5.8.5 or earlier.Affected if The installed version is 5.8.5 or earlier.
-
Identify read-only user accountsReview the user management section of Nagios XI to list all users and their assigned roles. Look for accounts with read-only or equivalent non-administrative roles.Affected if There is at least one user with a read-only role in the system.
-
Inspect downtime schedulesExamine the downtime scheduling feature in Nagios XI to view all scheduled downtime entries.Affected if There are downtime schedules present, particularly those that may have been created by read-only users.
The environment is affected if Nagios XI version is 5.8.5 or earlier and read-only users exist, as the incorrect permission check allows these users to schedule downtime.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Nagios XI to version 5.8.6 or later which contains the permission fix, then audit all downtime schedules and user accounts to ensure no unauthorized downtime was scheduled by read-only users.
Nagios XI 5.8.6 or later (preferably latest stable 5.x release)
- Back up the current Nagios XI configuration and database before upgrading
- Download the latest Nagios XI version from the official Nagios website (downloads.nagios.com) or your Nagios XI customer portal
- Run the automated upgrade script (./upgrade_xl) or use the web-based upgrade interface via Admin > System Extensions > System Upgrade
- Verify the upgrade completed successfully by checking the version number in the web interface (Admin > System Info)
- Confirm the fix by testing that a read-only user cannot schedule downtime - create a test read-only user and attempt to schedule downtime (should be denied)
- Review the audit logs to confirm authorization checks are now properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29271 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29271 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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