Jahlives openssl_encrypt
openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass
openssl_encrypt (pip: openssl-encrypt) versions <= 1.4.8 use suffix-tolerant fingerprint matching in enroll_trust_key when binding a plugin-signing trust anchor. An operator who confirms a short (forgeable, ~32-bit) GPG key id could unknowingly enroll an attacker's colliding key as a trusted anchor, which then vouches for malicious plugins under the ENFORCE signature policy. Version 1.4.9 fixes this by requiring the confirmed value to exactly match the full primary-key fingerprint (case-insensitive, whitespace-stripped).
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.3critical · scored by CNA · CWE-347
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
jahlives openssl_encrypt
- < 1.4.9
Fixed in 1.4.9
Mitigation
Upgrade openssl_encrypt to 1.4.9 or later.
References
- Vendor advisory github.com/jahlives/openssl_encrypt/security/a…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.