Summary
ntopng before 6.7.260717 does not properly verify privileges in its host-pools bulk-delete endpoint. An authenticated non-administrator may be able to delete all host pools and their member bindings, potentially removing traffic policy associations and visibility restrictions.
Affected context
The vulnerability occurs in ntopng deployments where authenticated users can reach the pools bulk-delete endpoint and the endpoint does not enforce an administrator-only authorization check. Environments that rely on host pools for traffic policies or visibility restrictions may be particularly exposed if a lower-privileged account can invoke the operation.
Exploit preconditions
- Attack surface: The ntopng web/API endpoint for bulk deletion of host pools
- Required access: A valid authenticated account; administrator privileges should not be required because of the authorization failure
- Trigger point: A POST request to the pools bulk-delete operation
- Why exploitation is possible: The endpoint fails to verify that the authenticated user has sufficient privileges before performing a destructive action
Why this happens
The underlying bug is an authorization enforcement failure. The bulk-delete handler performs a highly privileged state-changing operation without consistently checking the caller's role or permission set, allowing an authenticated but unauthorized user to invoke functionality intended for administrators. This behavior maps to CWE-862: Missing Authorization, in which access control is absent or insufficient for a protected resource or operation.
Potential impact
- An attacker may delete all configured host pools
- Member-to-pool bindings could be removed
- Traffic policies associated with host pools may no longer apply
- Visibility restrictions could be weakened or bypassed
- Network monitoring configuration may be disrupted
- Administrators may incur recovery and reconfiguration effort
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the server-side operation boundary.
Common defensive patterns include:
- Require an explicit administrative capability for bulk deletion
- Apply authorization checks independently of client-interface controls
- Use deny-by-default access policies for destructive operations
- Require confirmation and, where appropriate, additional approval for bulk changes
- Preserve auditable records of authorization decisions and destructive actions
- Run service components with only the privileges necessary for their responsibilities
- Reduce reliance on client-supplied role or permission indicators
How teams detect issues like this
Organizations can look for this issue through:
- Static analysis that identifies state-changing handlers without authorization guards
- Code review checks for bulk, delete, and administrative endpoints
- Tests that exercise privileged operations with each supported user role
- API gateway or policy rules restricting destructive endpoints to approved roles
- Monitoring for unusual bulk-delete requests or sudden disappearance of host-pool objects
- Audit-log review that compares the caller's role with the required permission for the operation

