CVE-2020-36859

8.8 HIGH

📋 TL;DR

This SQL injection vulnerability in Nagios XI's Core Config Manager allows authenticated users to inject malicious SQL queries through object edit pages. Successful exploitation could lead to unauthorized access, data disclosure, or modification of configuration data. Organizations running Nagios XI versions prior to 5.7.4 are affected.

💻 Affected Systems

Products:
  • Nagios XI
Versions: Nagios XI versions prior to 5.7.4, Core Config Manager versions prior to 3.0.7
Operating Systems: Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user access to the Core Config Manager interface.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the Nagios XI database, leading to disclosure of all monitoring data, configuration secrets, and potential lateral movement to other systems via database connections.

🟠

Likely Case

Unauthorized access to sensitive monitoring data, modification of alert configurations to hide security incidents, or extraction of credentials stored in the configuration.

🟢

If Mitigated

Limited impact due to proper input validation, database permissions, and network segmentation preventing lateral movement.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but SQL injection is straightforward once authenticated.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Nagios XI 5.7.4 or Core Config Manager 3.0.7

Vendor Advisory: https://www.nagios.com/changelog/nagios-xi/

Restart Required: Yes

Instructions:

1. Backup current Nagios XI installation. 2. Download Nagios XI 5.7.4 or later from Nagios website. 3. Follow Nagios XI upgrade documentation. 4. Restart Nagios services after upgrade.

🔧 Temporary Workarounds

Input Validation Web Application Firewall

all

Deploy WAF rules to detect and block SQL injection patterns in POST requests to object edit pages.

Restrict Access to Core Config Manager

all

Limit access to CCM interface to only necessary administrative users using network ACLs or authentication proxies.

🧯 If You Can't Patch

  • Implement strict database permissions limiting CCM application user to only necessary operations
  • Deploy network segmentation to isolate Nagios XI database from other critical systems

🔍 How to Verify

Check if Vulnerable:

Check Nagios XI version via Admin > System Config > About page or run: cat /usr/local/nagiosxi/var/xiversion

Check Version:

cat /usr/local/nagiosxi/var/xiversion

Verify Fix Applied:

Verify version is 5.7.4 or higher and check that SQL injection attempts are properly sanitized in object edit functionality.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts followed by CCM access
  • Unexpected configuration changes in object edit logs

Network Indicators:

  • Unusual database connection patterns from Nagios XI server
  • SQL error messages in HTTP responses

SIEM Query:

source="nagios_logs" AND ("SQL syntax" OR "unexpected character" OR "object edit")

🔗 References

📤 Share & Export