dbcve.org
HorizonApplication · Opennms

CVE-2020-11886

HIGH · 8.1 CVSS v3.1 Published 2020-04-17
Fix available
A fix is available. Upgrade to 25.2.1 / 2017.1.21 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenNMS Horizon and Meridian allows HQL Injection in element/nodeList.htm (aka the NodeListController) via snmpParm or snmpParmValue to addCriteriaForSnmpParm. This affects Horizon before 25.2.1, Meridian 2019 before 2019.1.4, Meridian 2018 before 2018.1.16, and Meridian 2017 before 2017.1.21.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenNMS Horizon and Meridian contain an HQL (Hibernate Query Language) injection vulnerability in the NodeListController (element/nodeList.htm) via the addCriteriaForSnmpParm method. Attackers can inject malicious HQL through the snmpParm or snmpParmValue parameters, potentially allowing unauthorized database access or manipulation.

MitigationUpdate to Horizon 25.2.1 or later, or Meridian 2019.1.4/2018.1.16/2017.1.21 or later per the affected version branch. Alternatively, implement strict input validation and parameterized queries for the snmpParm and snmpParmValue parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HorizonApplication
Affected:< 25.2.1
MeridianApplication
Affected:>= 2017, < 2017.1.21>= 2018, < 2018.1.16>= 2019, < 2019.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenNMS installation and version
    Locate the OpenNMS installation directory and check for a version file. Common locations include /opt/opennms/etc/opennms.properties or check the administrative web interface under 'About' or 'System Information' pages. The Meridian version is typically displayed in the footer of the web UI. For Horizon, check the pom.xml in the installation root or run 'opennms -v' if available.
    Affected if The installed version is OpenNMS Horizon < 25.2.1 OR Meridian 2017.x < 2017.1.21 OR Meridian 2018.x < 2018.1.16 OR Meridian 2019.x < 2019.1.4
  2. Verify the NodeListController endpoint is accessible
    Check if the OpenNMS web console is exposed by attempting to access the element/nodeList.htm endpoint. This is typically found at http(s)://<server>/opennms/element/nodeList.htm. Review your web server configuration to determine if this endpoint is reachable.
    Affected if The web interface and specifically the /element/nodeList.htm endpoint are accessible from an untrusted network or the internet
  3. Confirm parameter handling in the vulnerable method
    Inspect the application logs or web access logs for requests containing the parameters 'snmpParm' or 'snmpParmValue' sent to the nodeList.htm endpoint. These parameters are processed by the addCriteriaForSnmpParm method in NodeListController.
    Affected if Requests with snmpParm or snmpParmValue parameters to nodeList.htm are being logged, indicating the vulnerable code path is in use

You are affected if your OpenNMS installation version falls within the vulnerable ranges AND the web interface with the nodeList.htm endpoint is accessible and actively processing snmpParm/snmpParmValue parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 25.2.1 / 2017.1.21 / 2018.1.16 or later
Fixed in 25.2.12017.1.212018.1.16
Interim mitigation

Update to Horizon 25.2.1 or later, or Meridian 2019.1.4/2018.1.16/2017.1.21 or later per the affected version branch. Alternatively, implement strict input validation and parameterized queries for the snmpParm and snmpParmValue parameters.

Fix this in Horizon Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-11886 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data