Summary
A missing ownership check in the revoke_key method of openssl_encrypt allows an authenticated client to revoke another client's cryptographic key. The issue becomes risky when a client can submit a valid ML-DSA signature for a key it does not own, potentially disrupting other users' access.
Affected context
This vulnerability affects openssl_encrypt deployments using versions before 1.4.0 where the revoke_key method does not adequately verify key ownership. Exploitation requires an authenticated client interface that accepts key-revocation requests and processes valid ML-DSA signatures without binding the requested key to the requesting client's identity.
Exploit preconditions
- Attack surface: The authenticated key-management or revocation interface
- Required access: A valid client account capable of submitting revocation requests
- Trigger point: Invocation of the
revoke_keymethod for a key associated with another client - Required capability: A valid ML-DSA signature accepted by the revocation workflow
- Why exploitation is possible: The method validates the signature but does not reliably verify that the requester owns the targeted key
Why this happens
The underlying flaw is an authorization design failure in which authentication or cryptographic validity is treated as sufficient permission to act on a resource. The revoke_key method lacks an effective ownership check tying the requested key to the authenticated client, allowing a valid client to affect another client's key. This maps to CWE-639: Authorization Bypass Through User-Controlled Key, because a user-controlled key identifies a protected resource without an adequate authorization decision.
Potential impact
- An attacker may revoke cryptographic keys belonging to other clients.
- Legitimate clients could lose access to protected services or encrypted data.
- The vulnerability could cause targeted denial of service.
- Applications may experience failed authentication, signing, or decryption operations.
- Repeated abuse could undermine trust in the key-management service.
General mitigation guidance
Mitigation generally focuses on enforcing resource-level authorization independently of signature validation.
Common defensive patterns include:
- Verify that the authenticated principal owns or is explicitly authorized to manage the requested key.
- Bind key identifiers, client identities, and authorization decisions through server-side records rather than request data alone.
- Treat valid cryptographic signatures as proof of key possession, not proof of ownership or administrative permission.
- Apply least-privilege rules to key-management operations and separate administrative revocation from client self-service actions.
- Use consistent authorization checks for revoke, rotate, delete, and export operations.
- Record and alert on cross-client access attempts and repeated key-revocation failures.
How teams detect issues like this
Organizations can detect this class of issue through:
- Static analysis and code review checks for resource operations that validate signatures without an ownership or role check.
- Review of authorization middleware and service methods that accept client-controlled key identifiers.
- Tests that attempt cross-tenant or cross-client revocation using otherwise valid credentials.
- Policy enforcement requiring every key-management operation to compare the authenticated identity with server-side ownership metadata.
- Audit-log monitoring for revocations initiated by principals that are not recorded as owners or authorized administrators.
Automated code review tools may help identify missing object-level authorization checks, but behavioral authorization tests remain important.

