Overview 10 matches · 7 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
10matches
7in Waratek scope70.0%
1protected10.0%
0exploited0.0%
0CISA KEV0.0%
2public PoC20.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
1
10.0%
Rule in development
0
0.0%
Mitigation candidate
2
20.0%
No exploit published
4
40.0%
Outside Waratek scope
0
0.0%
Not applicable
3
30.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
10.0%
partly blocked
0
0.0%
not blocked
9
90.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
20.0%
Proof of concept only
1
10.0%
Forecast only
0
0.0%
No public exploit
7
70.0%
split by
peak 4 / year
20151
Not applicable1
High1
not blocked1
No public exploit1
20160
20170
20180
20190
20201
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
20214
No exploit published2
Not applicable2
High4
not blocked4
Proof of concept only1
No public exploit3
20220
20234
Mitigation candidate2
No exploit published2
High4
not blocked4
Working exploit published2
No public exploit2
201520162017201820192020202120222023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-40315 | High | 2023-08-17 | Mitigation candidate | Working exploit published | In OpenMNS Horizon 31.0.8 and versions earlier than 32.0.2 and related Meridian versions, any user that has the ROLE_FILESYSTEM_EDITOR can easily escalate their privileges to ROLE_ADMIN or any other role. The solution is to upgrade to Meridian 2023.1.5 or Horizon 32.0.2 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet. OpenNMS thanks Erik Wynter for reporting this issue. |
| CVE-2023-40313 | High | 2023-08-17 | No exploit published | No public exploit | A BeanShell interpreter in remote server mode runs in OpenMNS Horizon versions earlier than 32.0.2 and in related Meridian versions which could allow arbitrary remote Java code execution. The solution is to upgrade to Meridian 2023.1.6, 2022.1.19, 2021.1.30, 2020.1.38 or Horizon 32.0.2 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet. |
| CVE-2023-0872 | High | 2023-08-14 | Mitigation candidate | Working exploit published | The Horizon REST API includes a users endpoint in OpenMNS Horizon 31.0.8 and versions earlier than 32.0.2 on multiple platforms is vulnerable to elevation of privilege. The solution is to upgrade to Meridian 2023.1.6, 2022.1.19, 2021.1.30, 2020.1.38 or Horizon 32.0.2 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet. OpenNMS thanks Erik Wynter for reporting this issue. |
| CVE-2023-0870 | High | 2023-03-22 | No exploit published | No public exploit | A form can be manipulated with cross-site request forgery in multiple versions of OpenNMS Meridian and Horizon. This can potentially allow an attacker to gain access to confidential information and compromise integrity. The solution is to upgrade to Meridian 2023.1.1 or Horizon 31.0.6 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet. |
| CVE-2016-6556 | High | 2021-09-24 | Not applicable | No public exploit | OpenNMS version 18.0.1 and prior are vulnerable to a stored XSS issue due to insufficient filtering of SNMP agent supplied data. By creating a malicious SNMP 'sysName' or 'sysContact' response, an attacker can store an XSS payload which will trigger when a user of the web UI views the data. This issue was fixed in version 18.0.2, released on September 20, 2016. |
| CVE-2016-6555 | High | 2021-09-24 | Not applicable | No public exploit | OpenNMS version 18.0.1 and prior are vulnerable to a stored XSS issue due to insufficient filtering of SNMP trap supplied data. By creating a malicious SNMP trap, an attacker can store an XSS payload which will trigger when a user of the web UI views the events list page. This issue was fixed in version 18.0.2, released on September 20, 2016. |
| CVE-2021-25931 | High | 2021-05-20 | No exploit published | Proof of concept only | 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 at `/opennms/admin/userGroupView/users/updateUser`. This flaw allows assigning `ROLE_ADMIN` security role to a normal user. Using this flaw, an attacker can trick the admin user to assign administrator privileges to a normal user by enticing him to click upon an attacker-controlled website. |
| CVE-2021-3396 | High | 2021-02-17 | No exploit published | No public exploit | OpenNMS Meridian 2016, 2017, 2018 before 2018.1.25, 2019 before 2019.1.16, and 2020 before 2020.1.5, Horizon 1.2 through 27.0.4, and Newts <1.5.3 has Incorrect Access Control, which allows local and remote code execution using JEXL expressions. |
| CVE-2020-12760 | High | 2020-05-11 | Protected by Waratek | No public exploit | An issue was discovered in OpenNMS Horizon before 26.0.1, and Meridian before 2018.1.19 and 2019 before 2019.1.7. The ActiveMQ channel configuration allowed for arbitrary deserialization of Java objects (aka ActiveMQ Minion payload deserialization), leading to remote code execution for any authenticated channel user regardless of its assigned permissions. |
| CVE-2015-7856 | High | 2015-10-16 | Not applicable | No public exploit | OpenNMS has a default password of rtc for the rtc account, which makes it easier for remote attackers to obtain access by leveraging knowledge of the credentials. |