mediumVulnerability

GHSA-hvc7-763r-4f3h

### 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.

Properties

ghsa_id
GHSA-hvc7-763r-4f3h
severity
medium
summary
openssl-encrypt has no owner verification on key revocation — any client can revoke any key
cve_id
GHSA-hvc7-763r-4f3h
is_ghsa_only
true
ghsa_published
2026-04-01T21:11:32Z
source_url
https://github.com/advisories/GHSA-hvc7-763r-4f3h
ghsa_updated
2026-04-01T21:11:33Z

Related Entities (3)

REPORTED_BY (1)

[Source]GitHub Advisory Database

AFFECTS (1)

[Software]pip/openssl-encrypt

HAS_WEAKNESS (1)

[Weakness]Missing Authorization

Explore deeper with Ninja Signal's threat intelligence graph