Summary
An improper access control issue in MISP's authentication key reset functionality allowed organization administrators to reset and obtain authentication keys for site administrator accounts within the same organization.
Under these conditions, a lower-privileged admin could generate a new auth key for a higher-privileged account and use it to escalate privileges.
Affected context
This vulnerability appears in MISP deployments where:
- The platform is configured with multiple roles, including organization administrators and site administrators
- Authentication keys are used for API or programmatic access
- The auth key reset mechanism does not strictly enforce role-based authorization checks on which accounts can be managed
The issue specifically affects scenarios where an organization administrator can access or trigger auth key resets for site administrator accounts within the same organization.
Exploit preconditions
- Attack surface: MISP web interface or API endpoint responsible for authentication key reset.
- Required access: Valid login as an organization administrator within the affected organization (non-site admin).
- Trigger point: Invoking the auth key reset action targeting a site administrator account in the same organization.
- Why exploitation is possible: The authorization layer fails to distinguish between organization and site administration privileges for this function, allowing a lower-privileged role to perform operations intended only for higher-privileged accounts.
Why this happens
The root cause maps to CWE-863: Improper Authorization, where the system performs a permission check that does not properly account for the specific role or context of the caller.
In this case, the auth key reset feature validates that the requester is an organization administrator but does not enforce an additional constraint that only site administrators may reset auth keys for site admin accounts.
This incomplete authorization model permits a user with insufficient privilege to perform administrative actions on more privileged accounts, leading to horizontal and effective vertical privilege escalation.
Potential impact
- An organization administrator could generate and obtain a new auth key for a site administrator account.
- The attacker could impersonate a site administrator via API or token-based access.
- Privilege escalation from organization admin to site admin capabilities could occur.
- Misuse of elevated privileges could lead to unauthorized data access, configuration changes, or manipulation of shared threat intelligence.
General mitigation guidance
Mitigation centers on enforcing strict, role-aware authorization for administrative operations involving sensitive credentials or tokens.
Common defensive patterns include:
- Implementing fine-grained role-based access control (RBAC), ensuring only site administrators can manage auth keys for site admin accounts.
- Applying contextual checks that verify both the actor's role and the target account's role before allowing key resets.
- Introducing least-privilege defaults for administrative interfaces so that organization-level admins cannot perform global or higher-tier operations by default.
- Separating duties for credential lifecycle management, with dedicated flows for high-privilege accounts that require stronger approvals or additional controls.
- Logging and monitoring all auth key resets, combined with alerting on unusual patterns (such as one role frequently resetting keys for higher-privileged accounts).
How teams detect issues like this
Detection of similar authorization weaknesses can leverage:
- Static analysis and code review: Look for endpoints that manipulate credentials, tokens, or auth keys and ensure they include explicit, role-aware authorization checks against both the caller and target resource.
- Security testing: Perform role-based penetration tests and automated integration tests to validate that lower-privileged roles cannot invoke functions meant for higher-privileged accounts.
- Policy enforcement: Define coding guidelines requiring explicit authorization functions for all administrative operations, especially those involving authentication secrets.
- Operational monitoring: Enable detailed audit logging for account and key management actions, and use automated tooling to flag anomalous relationships (e.g., non-site admins initiating actions on site admin accounts).

