Cross-Site Request Forgery in OpenNMS Horizon
OpenNMS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.opennms:opennms Maven |
|
|
| org.opennms:opennms-config Maven |
|
|
OpenNMS
| Product | Affected | Fixed in |
|---|---|---|
| org.opennms:opennms Maven |
|
|
| org.opennms:opennms-config Maven |
|
|
In OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.0-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.
From the CVE record · Mend
OpenNMS Horizon and Meridian lack CSRF protection and do not check whether a username already exists during renaming. A forged rename request can overwrite the renamed user's privileges with those of the old user and remove the old user from the user list. The input does not specify authentication requirements or whether user interaction is needed.
Check OpenNMS Horizon from opennms-1-0-stable through opennms-27.1.0-1, OpenNMS Meridian from meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1 or meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1, and Maven org.opennms:opennms or org.opennms:opennms-config versions >=1.0.0 and <27.1.1.