Summary
ntopng contains missing authorization checks in REST v2 handlers that delete notification endpoints and recipients. An authenticated non-administrator user may submit requests that irreversibly remove alert destinations, potentially silencing configured notifications.
Affected context
The issue occurs in ntopng deployments where authenticated users can reach the REST v2 delete endpoints or recipients handlers. The risk is present when those handlers rely on authentication without separately verifying that the caller has administrator-level authorization before allowing destructive configuration changes.
Exploit preconditions
- Attack surface: ntopng REST v2 API
- Required access: A valid authenticated account, including a non-administrator account
- Trigger point: Delete operations for configured notification endpoints or recipients
- Why exploitation is possible: The affected handlers do not adequately enforce authorization before processing irreversible deletion requests
Why this happens
The underlying bug is a missing authorization check, mapped to CWE-862: Missing Authorization. The application verifies or accepts the user's authenticated session but fails to enforce the required privilege level for sensitive deletion operations, allowing a lower-privileged principal to perform an action reserved for administrators.
Potential impact
- Notification endpoints and recipients may be irreversibly deleted
- Security and operational alerts could be silenced
- Monitoring coverage may be reduced without immediate visibility
- Lower-privileged accounts could modify security-relevant configuration
- Incident response and compliance workflows may be disrupted
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every sensitive API operation, not only at login or route-access boundaries.
Common defensive patterns include:
- Require explicit administrator authorization for destructive notification-management actions
- Apply server-side, deny-by-default access-control checks to each delete handler
- Enforce object-level authorization for notification endpoints and recipients
- Use separate permissions for viewing, creating, modifying, and deleting alert configuration
- Add confirmation and audit controls for irreversible administrative changes
- Run authorization tests for authenticated users with different privilege levels
- Minimize account privileges and restrict administrative roles to users who need them
How teams detect issues like this
Organizations can look for this weakness through:
- Static analysis and code review checks for destructive handlers lacking centralized authorization middleware
- Tests that exercise delete operations with authenticated non-administrator accounts
- API policy checks requiring administrator permissions for notification configuration changes
- Monitoring for unexpected deletion requests affecting notification endpoints or recipients
- Audit-log review for destructive configuration changes and unusual activity by lower-privileged users
- Automated security testing that compares endpoint behavior across authorization roles

