CVE-2022-29272
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, an open redirect vulnerability exists in the login function that could lead to spoofing.
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 · moderate confidenceNagios XI versions through 5.8.5 contain an open redirect vulnerability in the login function. The application does not properly validate the redirect URL parameter, allowing an attacker to craft malicious URLs that appear to originate from the legitimate Nagios XI login page but redirect users to arbitrary external sites after authentication. This can be leveraged for phishing attacks to steal credentials or deliver malware.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm Nagios XI installationIdentify if Nagios XI is present on the system by checking for the Nagios XI web directory (commonly at /var/www/html/nagiosxi/ or /usr/local/nagiosxi/) or by querying for the nagiosxi service/process.Affected if Nagios XI is installed on the system.
-
Determine installed Nagios XI versionLocate and read the version file in the Nagios XI installation directory, or access the Nagios XI web interface and check the version information typically displayed in the footer or admin section.Affected if The installed version is 5.8.5 or any earlier version (5.x through 5.8.5).
-
Verify login function is accessibleConfirm the Nagios XI login page is reachable by accessing the web interface URL (commonly /nagiosxi/ or /login.php) via HTTP/HTTPS.Affected if The login page is accessible over the network.
-
Check for redirect URL parameter handlingInspect the login form or URL parameters to identify if a redirect parameter (commonly 'redirect' or 'url') is accepted and processed after authentication.Affected if The login function accepts and processes a redirect URL parameter without strict validation.
A user is affected if Nagios XI version 5.8.5 or lower is installed and the login function is accessible, as the open redirect vulnerability exists in these versions.
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 · scopedImplement strict validation of any redirect URLs in the login function to ensure they remain within the application's trusted domain before performing the redirect. Consider implementing a whitelist approach or only allowing relative URLs.
Nagios XI 5.8.6 or later
- 1. Check current Nagios XI version: /usr/local/nagiosxi/nagiosversion.sh or via the web UI (Admin > System Info)
- 2. Back up the entire Nagios XI system including the database before upgrading
- 3. Download the latest Nagios XI version from the official Nagios website (assets.nagios.com) or use the auto-update feature if available
- 4. Apply the upgrade following the official Nagios XI upgrade documentation
- 5. Verify the upgrade was successful and the login redirect functions properly
- 6. Test that the open redirect vulnerability is no longer present by attempting to use a crafted redirect URL
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29272 — 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-29272 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