Horizon: Improper Control of Generation of Code
CVE-2023-40313 is a high-severity improper control of generation of code vulnerability in Horizon from The OpenNMS Group, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 32.0.2 as the first without the flaw, so updating Horizon to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.78% chance of exploitation within 30 days, higher than 57% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Horizon to 32.0.2 or a later version.
- Update horizon to 32.0.2 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| The OpenNMS Group | Horizon | 29.0.4 up to, but not including, 32.0.2 | 32.0.2 |
| The OpenNMS Group | Meridian | 2020.0.0 through 2020.1.37; 2021.0.0 through 2021.1.29; 2022.0.0 through 2022.1.18; 2023.0.0 through 2023.1.5 | Not stated |
| Opennms | horizon | 29.0.4 up to, but not including, 32.0.2 | 32.0.2 |
| Opennms | meridian | 2020.0.0 through 2020.1.37; 2021.0.0 through 2021.1.29; 2022.0.0 through 2022.1.18; 2023.0.0 through 2023.1.5 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.1 | High | CNA (opennms.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- docs.opennms.com/horizon/32/releasenotes/changelog.htmlRelease Notes
- github.com/OpenNMS/opennms/pull/6368Issue Tracking
Other vulnerabilities in Horizon
- 9.1 Critical severity
- 8.2 High severity
- 8.0 High severity
- 8.0 High severity
- 8.0 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.