Summary
UnoPim before 2.1.3 does not include integration store, update, and key-generation routes in its access-control map. An authenticated user with minimal administrative privileges may bypass authorization checks, create OAuth API integrations, mint client credentials, and potentially obtain higher-level access.
Affected context
The vulnerability occurs in UnoPim administrative functionality when integration-related routes are not represented in the ACL map used by the Bouncer authorization middleware. Deployments may be exposed when a low-privilege administrative account can reach these routes and the middleware relies on incomplete route-to-permission mappings.
Exploit preconditions
- Attack surface: Administrative web or API routes for integration management
- Required access: An authenticated account with minimal administrative privileges
- Trigger point: Requests to integration store, update, or OAuth key-generation endpoints
- Why exploitation is possible: The affected routes are absent from the ACL map, allowing requests to bypass expected permission validation
Why this happens
The underlying bug is an incomplete authorization policy map. Because integration management and credential-generation routes are omitted from the Bouncer middleware's ACL configuration, authorization decisions are not consistently applied to those operations. This behavior maps to CWE-862: Missing Authorization, where a protected function can be reached without an effective permission check.
Potential impact
- A low-privilege administrator may create unauthorized OAuth API integrations
- Attackers may mint client credentials with broader access than intended
- Account or tenant privileges could be escalated
- Unauthorized API activity could expose or modify protected data
- Compromised credentials could support persistence or lateral access
General mitigation guidance
Mitigation generally focuses on making authorization explicit, centralized, and fail-closed.
Common defensive patterns include:
- Registering every sensitive route and operation in a complete ACL or policy model
- Denying access by default when a route lacks an authorization rule
- Enforcing permission checks at the service or controller boundary rather than relying only on route metadata
- Separating integration administration and credential-generation privileges
- Limiting the scope and lifetime of issued OAuth credentials
- Applying least privilege to administrative roles and service accounts
- Reducing trust in client-supplied role or permission context
How teams detect issues like this
Organizations can identify similar authorization gaps through:
- Static analysis and route inventory checks that compare sensitive endpoints with ACL or policy definitions
- Code review checks for newly added routes without corresponding authorization rules
- Tests that exercise each administrative endpoint with multiple privilege levels
- Negative authorization tests confirming that unmapped or unknown routes are denied
- Runtime monitoring for unexpected integration creation, key generation, or privilege changes
- Policy enforcement requiring security review for credential-management functionality

