openssl-encrypt has no owner verification on key revocation — any client can revoke any key
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-862.
Summary
### Summary The `revoke_key` method in `openssl_encrypt_server/modules/keyserver/service.py` at **lines 195-270** accepts a `client_id` parameter but never verifies that the requesting client is the same as `key.owner_client_id`. ### Impact Any authenticated client can revoke any other client's key, as long as they provide a valid revocation signature. While the signature requirement mitigates this somewhat (you need the private key to sign), the lack of ownership check is a defense-in-depth gap. ### Recommended Fix - Add an ownership check: verify `client_id == key.owner_client_id` before allowing revocation - Return 403 Forbidden if the requesting client does not own the key ### Fix Fixed in commit `05e45f3` on branch `releases/1.4.x` — added documentation that ML-DSA signature verification IS the cryptographic ownership check; added info-level logging on successful verification.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | openssl-encrypt (PyPI) | before 1.4.0 | 1.4.0 | Patch available | GHSA-hvc7-763r-4f3h |
- openssl-encrypt (PyPI) Vendor— Affected before 1.4.0 Fixed in 1.4.0 Patch available GHSA-hvc7-763r-4f3h
Remediation
- Fix · GHSA-hvc7-763r-4f3h openssl-encrypt (PyPI) Fixed in 1.4.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-hvc7-763r-4f3h
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences