Where
-Infinity
0

Vendor Risk Score

See how openssl_encrypt compares to other vendors in security performance

View Risk Score →
Severity
8.7
Path Traversal
AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

opensslencrypt (pip: openssl-encrypt) versions before 1.4.9 contain a path traversal flaw in PluginSandbox.issafepath, which authorized file access using a bare string-prefix match. A sandboxed plugin without the READFILES permission could read or write another plugin's directory that merely shares a name prefix (e.g., .../plugins/foobar matching allowed .../plugins/foo), breaking per-plugin isolation within the same user. Fixed by matching each allowed directory exactly or with a trailing path separator.

First published (updated )
Severity
9.3
AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

opensslencrypt (pip: openssl-encrypt) versions <= 1.4.8 use suffix-tolerant fingerprint matching in enrolltrustkey 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 published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203