Summary
Peppermint contains a broken access control vulnerability in its ticket, client, and user handlers because permission enforcement is disabled by default. Any authenticated user may be able to read, modify, or delete records owned by other accounts on affected default installations.
Affected context
The issue occurs in Peppermint deployments where the Config.roles_active setting remains disabled. In that state, authorization checks in relevant handlers may become no-ops, allowing authenticated users to operate on resources outside their intended ownership or administrative scope. The affected functionality includes ticket, client, and user management.
Exploit preconditions
- Attack surface: Authenticated web application handlers for tickets, clients, and users
- Required access: Any valid Peppermint user account
- Trigger point: Requests to view, modify, or delete resources belonging to another account
- Why exploitation is possible: The default configuration disables role-based permission enforcement, allowing ownership and administrative checks to be bypassed
Why this happens
The underlying flaw is a configuration-dependent authorization failure. When Config.roles_active defaults to false, handler-level permission checks effectively do not enforce the intended access policy. This maps to CWE-284: Improper Access Control, because authenticated users are not restricted to resources and actions authorized for their account or role.
Potential impact
- Unauthorized disclosure of tickets, client records, and user information may occur
- Attackers could modify records owned by other accounts
- Attackers could delete tickets, clients, or users
- Data integrity and service availability could be affected
- Compromised accounts could be used to perform broad administrative actions
General mitigation guidance
Mitigation generally focuses on making authorization enforcement active and fail-closed by default.
Common defensive patterns include:
- Enabling role and ownership checks by default rather than relying on optional configuration
- Enforcing authorization independently in every affected handler and service boundary
- Denying access when authorization state is missing, disabled, or ambiguous
- Separating authentication from resource-level authorization decisions
- Applying least privilege to user roles and administrative operations
- Testing cross-account access attempts for read, update, and delete actions
- Restricting configuration changes through controlled deployment and administrative processes
How teams detect issues like this
Organizations can identify similar issues through:
- Static analysis and code review searches for authorization checks gated by disabled-by-default flags
- Review of handlers that perform resource operations without explicit ownership or role validation
- Dynamic tests using multiple accounts to verify cross-tenant isolation
- Policy checks requiring authorization enforcement for every read, write, and delete endpoint
- Monitoring for authenticated users accessing unusually broad sets of unrelated resources
- Automated security review tools that flag missing or conditionally bypassed access-control logic

