Summary
ntopng contains missing authorization checks in REST v2 endpoints used to delete and rename tags. Any authenticated user, including an unprivileged account, may alter administrator-created tags when the affected endpoints are reachable.
Affected context
The issue occurs in ntopng deployments using the affected REST v2 tag management endpoints. The delete and edit operations do not appear to verify whether the authenticated caller has permission to manage the targeted tag, allowing lower-privileged users to affect tags created by other users or administrators.
Exploit preconditions
- Attack surface: ntopng web application REST v2 endpoints
- Required access: A valid authenticated ntopng user account
- Trigger point: Requests to the tag deletion or tag editing endpoints
- Target condition: The account must be able to reach the ntopng service and identify a tag
- Why exploitation is possible: The endpoints perform the requested operation without an effective authorization check
Why this happens
The underlying bug is an authorization enforcement failure. The application authenticates the caller but does not verify that the caller has sufficient privileges to modify the selected tag before performing the operation. This maps to CWE-862, Missing Authorization, in which a protected operation is exposed without enforcing the required access-control decision.
Potential impact
- An unprivileged user may delete tags used by administrators or other teams.
- An attacker could rename tags and disrupt monitoring workflows or dashboards.
- Tag-based filtering, classification, or alerting could be altered or made misleading.
- Operational users may lose confidence in the integrity of network-monitoring metadata.
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every tag management operation, rather than relying on authentication alone. The application should apply centralized, deny-by-default access-control checks before deletion or modification, verify ownership or administrative scope for the specific tag, and use least-privilege roles for routine accounts. Authorization decisions should be based on trusted server-side identity and policy data, not client-supplied privilege indicators. Administrative endpoints can also be isolated through network policy and stronger authentication controls where appropriate.
How teams detect issues like this
Detection can include static analysis and code review for REST handlers that mutate records without an adjacent authorization or ownership check. Dynamic testing should exercise tag deletion and editing with accounts of different privilege levels and confirm that denied operations produce no state change. Audit logging and policy enforcement can monitor tag-management requests, unexpected changes, and authorization failures. Automated security review tools may help identify endpoints that authenticate users but omit operation-level authorization.

