Skip to content
Fencer Intel
medium 5.3

CVE-2023-40315 json

ROLE_FILESYSTEM_EDITOR Can Be Used To Escalate To ROLE_ADMIN

published 3y ago modified 4mo ago also GHSA-hf5p-f83x-5q2g , EUVD-2023-2300

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 86%
public exploits
1
Metasploit

Summary

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.

Patch / fix

  • maven org.opennms:opennms-webapp-rest 32.0.2
  • The OpenNMS Group Horizon 32.0.2
  • The OpenNMS Group Meridian 2023.1.5

Is CVE-2023-40315 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/linux/http/opennms_horizon_authenticated_rce)
  2. Published

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

2.85% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:L
NVD 3.1 8.0 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 5.3 CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:L

Affected packages

ecosystem package affected fixed in
maven org.opennms:opennms-webapp-rest
>=31.0.8, <32.0.2
32.0.2

Affected products

  • The OpenNMS Group Horizon
  • The OpenNMS Group Meridian

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.