Skip to content

Cross-Site Request Forgery in OpenNMS Horizon

Moderate severity GitHub Reviewed Published May 25, 2021 to the GitHub Advisory Database • Updated Sep 26, 2023

Package

maven org.opennms:opennms (Maven)

Affected versions

>= 1.0.0, < 27.1.1

Patched versions

27.1.1
maven org.opennms:opennms-config (Maven)
>= 1.0.0, < 27.1.1
27.1.1

Description

In OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to CSRF, due to no CSRF protection, and since there is no validation of an existing user name while renaming a user. As a result, privileges of the renamed user are being overwritten by the old user and the old user is being deleted from the user list.

References

Published by the National Vulnerability Database May 20, 2021
Reviewed May 21, 2021
Published to the GitHub Advisory Database May 25, 2021
Last updated Sep 26, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS score

0.107%
(45th percentile)

Weaknesses

CVE ID

CVE-2021-25930

GHSA ID

GHSA-p63h-7hw8-5cw4

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.