CVE-2023-0871: OpenNMS Horizon XXE Injection Vulnerability

Summary

11/08/2023
Yes i
High
8.8

CVE-2023-0871: OpenNMS Horizon XXE Injection Vulnerability. Affects org.opennms.core:org.opennms.core.xml versions >= 31.0.8, < 32.0.2. Fixed in 32.0.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

OpenNMS Horizon is an open-source network management platform that provides monitoring and management capabilities for various network devices and services. It includes the org.opennms.core.xml package, which is responsible for XML parsing and processing within the application. This package is vulnerable to an XML external entity (XXE) injection attack.

Vulnerability Detail

The XXE injection vulnerability exists in the /rtc/post/ endpoint of OpenNMS Horizon versions 31.0.8 and earlier than 32.0.2. An attacker can exploit this vulnerability to inject malicious XML entities, leading to various attacks such as information disclosure, server-side request forgery (SSRF), and remote code execution. By crafting specially crafted XML payloads, an attacker can force OpenNMS Horizon to make arbitrary HTTP requests to internal and external services.

How To Fix

Minimum fixed version

32.0.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the available patches or upgrade to the fixed versions mentioned above.

Conclusion

The XXE injection vulnerability in OpenNMS Horizon can be mitigated by upgrading to the recommended fixed versions or applying the available patches. It is important to follow the installation instructions provided by OpenNMS and ensure that the software is not directly accessible from the Internet. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for org.opennms.core:org.opennms.core.xml →

Share this vulnerability

FAQ

An XXE injection vulnerability allows an attacker to exploit XML parsing functionality to inject malicious XML entities, leading to various attacks such as information disclosure, SSRF, and remote code execution.

This vulnerability allows an attacker to force OpenNMS Horizon to make arbitrary HTTP requests to internal and external services, potentially leading to unauthorized access, data leakage, or further exploitation of the affected system.

Yes, upgrading to the fixed versions mentioned in the 'how_to_fix' section or applying the available patches will mitigate this vulnerability.

Yes, this vulnerability can be exploited remotely by sending specially crafted XML payloads to the vulnerable /rtc/post/ endpoint.

There is no evidence of active exploitation of this vulnerability at the moment. However, it is crucial to apply the recommended fixes to prevent potential attacks.

How To Fix

Minimum fixed version

32.0.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback