Summary
OpenNMS Horizon exposes certain PATCH configuration endpoints without enforcing authorization because the Spring Security policy does not cover that HTTP method. An unauthenticated attacker who can reach the web interface may disable event definitions or SNMP data collection, weakening monitoring and alarm generation.
Affected context
The vulnerability occurs in OpenNMS Horizon deployments where:
- The web UI and
/api/v2REST API are reachable by an attacker - PATCH-based configuration endpoints are enabled
- Authorization rules cover other HTTP methods but omit PATCH
- Changes to event configuration or SNMP data-collection settings are persisted and applied to the running system
Deployments intended for private networks may still be exposed if network boundaries, authentication controls, or reverse-proxy policies are misconfigured.
Exploit preconditions
- Attack surface: The OpenNMS Horizon web UI and
/api/v2REST API - Required access: Network reachability to the web interface; authentication is not required by the affected endpoints
- Trigger point: PATCH requests to event-configuration or SNMP data-collection endpoints
- Why exploitation is possible: The security policy omits PATCH authorization rules, allowing configuration changes to bypass the intended access-control boundary
Why this happens
The underlying flaw is an incomplete authorization policy. Security rules were defined for most HTTP methods but did not include PATCH, leaving configuration endpoints using that method outside the enforced authorization model.
This maps to CWE-862: Missing Authorization, where an application fails to verify whether a requester is permitted to perform a protected operation. Because the affected operations alter persistent monitoring configuration, an unauthenticated request can change system behavior without the required access check.
Potential impact
- An attacker may disable event definitions and suppress alarm generation
- SNMP data collection may be disabled, reducing metric visibility
- Monitoring gaps could conceal operational failures or security events
- Persisted changes could continue affecting the running system after reloads or restarts
- Incident detection and response may be delayed
General mitigation guidance
Mitigation generally focuses on making authorization method-complete and applying access control consistently to every protected endpoint.
Common defensive patterns include:
- Enforcing authentication and authorization for PATCH operations as well as other HTTP methods
- Defining endpoint permissions centrally rather than relying on incomplete method-specific rules
- Applying deny-by-default policies to configuration APIs
- Restricting web-interface exposure to trusted private networks or controlled administrative paths
- Separating monitoring administration from general user access through least privilege
- Validating that persisted configuration changes are authorized, logged, and reviewable
- Applying vendor-supported security updates through the organization's normal patch-management process
How teams detect issues like this
Organizations can identify similar authorization gaps through:
- Static analysis and route inventory checks that compare exposed HTTP methods with security rules
- Code review of controller mappings and Spring Security matcher configurations
- Integration tests that exercise every method on administrative and configuration endpoints
- Negative authorization tests confirming unauthenticated and low-privilege users are denied
- API gateway or reverse-proxy policies that explicitly restrict administrative PATCH requests
- Audit monitoring for unexpected changes to event definitions and SNMP collection settings
Automated security testing tools may help detect method-specific access-control inconsistencies, but coverage should include authenticated, unauthenticated, and differently privileged request contexts.

