openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| jahlives | openssl_encrypt | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Jahlives | Openssl Encrypt |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.199% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jahlives
Jahlives openssl Encrypt |
|
| Vendors & Products |
Jahlives
Jahlives openssl Encrypt |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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). | |
| Title | openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|