CVE-2023-0870

8.1 HIGH

📋 TL;DR

This CVE describes a cross-site request forgery (CSRF) vulnerability in OpenNMS Meridian and Horizon monitoring platforms. Attackers can manipulate forms to perform unauthorized actions, potentially accessing confidential information or compromising system integrity. Organizations running vulnerable versions of these platforms are affected.

💻 Affected Systems

Products:
  • OpenNMS Meridian
  • OpenNMS Horizon
Versions: Meridian versions before 2023.1.1, Horizon versions before 31.0.6
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in web interface forms. Installation documentation recommends private network deployment only.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing unauthorized access to sensitive monitoring data, configuration changes, or administrative takeover of the OpenNMS platform.

🟠

Likely Case

Unauthorized data access or configuration changes within the OpenNMS platform, potentially affecting monitored systems and network visibility.

🟢

If Mitigated

Limited impact due to proper network segmentation and access controls, with only authorized users able to interact with the vulnerable interface.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

CSRF attacks require user interaction (victim must be logged in and visit malicious page).

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Meridian 2023.1.1 or Horizon 31.0.6

Vendor Advisory: https://docs.opennms.com/meridian/2023/releasenotes/changelog.html#releasenotes-changelog-Meridian-2023.1.1

Restart Required: Yes

Instructions:

1. Backup current configuration and data. 2. Download patched version from OpenNMS repository. 3. Stop OpenNMS service. 4. Install updated version following vendor documentation. 5. Restart OpenNMS service. 6. Verify functionality.

🔧 Temporary Workarounds

CSRF Protection Headers

all

Implement CSRF tokens or SameSite cookie attributes in web application configuration

Configuration changes in web.xml or application.properties

Network Segmentation

all

Restrict access to OpenNMS web interface to trusted internal networks only

firewall rules to block external access to OpenNMS ports

🧯 If You Can't Patch

  • Implement strict network access controls to limit OpenNMS web interface access to authorized users only
  • Deploy web application firewall (WAF) with CSRF protection rules and monitor for suspicious requests

🔍 How to Verify

Check if Vulnerable:

Check OpenNMS version via web interface admin panel or command line

Check Version:

opennms version

Verify Fix Applied:

Verify version is Meridian 2023.1.1+ or Horizon 31.0.6+ and test form submissions for CSRF tokens

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions from unexpected sources
  • Multiple failed authentication attempts followed by successful form submissions

Network Indicators:

  • HTTP requests to OpenNMS forms without proper referrer headers or CSRF tokens
  • Traffic from external sources to internal OpenNMS ports

SIEM Query:

source="opennms" AND (http_method="POST" OR http_method="PUT") AND NOT referrer="*opennms*"

🔗 References

📤 Share & Export