Skip to content

← Public intelligence

Maven package

org.opennms:opennms-webapp-rest

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3MavenPublished

    OpenNMS privilege escalation vulnerability

    CVE-2023-40315 · GHSA-hf5p-f83x-5q2g

    Affected
    • Maven org.opennms:opennms-webapp-rest >= 31.0.8, < 32.0.2
    Fixed in
    32.0.2· Vendor fix available
    Issue
    In OpenNMS Horizon 31.0.8 and versions earlier than 32.0.2 and related Meridian versions, any user that has the ROLEFILESYSTEMEDITOR can easily escalate their privileges to ROLEADMIN 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.

    Recommended action: Upgrade to 32.0.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.2MavenPublished

    OpenNMS privilege elevation vulnerability

    CVE-2023-0872 · GHSA-w5gq-xrrp-3fxf

    Affected
    • Maven org.opennms:opennms-webapp-rest >= 31.0.8, < 32.0.2
    Fixed in
    32.0.2· Vendor fix available
    Issue
    The Horizon REST API includes a users endpoint in OpenNMS 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.

    Recommended action: Upgrade to 32.0.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →