نسخههای متأثر
بازهها نیاز به بررسی دارند.
- نسخههای متأثر
- <1.4.0
- نسخهٔ اصلاحشده
- 1.4.0
- نسخههای متأثر
- < 1.4.0
- نسخهٔ اصلاحشده
- 1.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_idbefore allowing revocationReturn 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.
پیوندها
- https://github.com/advisories/GHSA-hvc7-763r-4f3h
- https://github.com/jahlives/openssl_encrypt
- https://github.com/jahlives/openssl_encrypt/commit/05e45f393886b5bf7e924d2dd42099a9dd37f91d
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-hvc7-763r-4f3h
- https://www.vulncheck.com/advisories/openssl-encrypt-before-missing-ownership-verification-via-revoke-key

