NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

GHSA-hvc7-763r-4f3h: openssl-encrypt has no owner verification on key revocation — any client can revoke any key

mediumCVSS 4.0 6.6

Summary The revokekey method in opensslencryptserver/modules/keyserver/service.py at lines 195-270 accepts a clientid parameter but never verifies that the requesting client is the same as key.ownerclientid. Impact Any authenticated client can revoke any other client's key, as long as they provide a valid revocation signature.

Published Apr 1, 2026

Affected packages

openssl-encrypt

Ecosystem
PyPI
Affected
< 1.4.0
Fixed in
1.4.0
Check
pip show openssl-encrypt

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries