EUVD-2026-60089
GHSA-q9f6-q6m5-f5h2
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Triggering the exposure requires local CLI invocation by an operator; leaked pepper is test-ephemeral and cannot decrypt production files, warranting C:L not C:H.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
openssl_encrypt (pip) versions <= 1.4.7 contain an information exposure vulnerability where the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally print the full derived hardware pepper as hex to stdout/stderr (crypt_cli.py, handle_hsm_command). The printed value can persist in terminal scrollback, session recordings, or CI logs. Impact is limited because the pepper is derived from a random per-invocation test salt and is salt-bound, so the leaked value cannot be used to decrypt real files. A related plugin issue logged raw prf_data outside the secret-redaction path. Fixed in 1.4.8 (and 1.5.0) by removing the hex dumps and routing plugin debug output through the redaction layer.
AnalysisAI
openssl_encrypt (pip, versions <= 1.4.7) unconditionally prints a derived hardware pepper as a hex string to stdout/stderr when the 'hsm fido2-test' or 'hsm onlykey-test' diagnostic commands are invoked, with output potentially persisting in CI build logs, terminal scrollback buffers, or session recordings. A secondary exposure exists where a related plugin component logged raw prf_data values outside the library's secret-redaction pathway. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that a user or automated process explicitly invoke one of two specific CLI diagnostic subcommands - 'hsm fido2-test' or 'hsm onlykey-test' - implemented in crypt_cli.py via handle_hsm_command on a host with openssl_encrypt <= 1.4.7 installed. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H) characterizes this as a remotely exploitable, unauthenticated, high-confidentiality-impact vulnerability, which conflicts materially with the description: triggering the exposure requires a local operator to explicitly invoke specific CLI diagnostic subcommands, suggesting the network attack vector and PR:N rating are overstated relative to the true exploitation model. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker with read access to archived CI/CD build logs or terminal session recordings from a system running openssl_encrypt <= 1.4.7 searches the output for hex strings printed by the 'hsm fido2-test' or 'hsm onlykey-test' commands. The attacker extracts the printed pepper value, but is unable to leverage it to decrypt any real files because the value is derived from a random per-invocation test salt with no relationship to production encryption material. … |
| Remediation | Upgrade openssl_encrypt to version 1.4.8 or 1.5.0 via pip: `pip install "openssl_encrypt>=1.4.8"`. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory all systems running openssl_encrypt <= 1.4.7, immediately disable the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands, and audit recent CI build logs and terminal sessions for exposed pepper values. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Openssl Encrypt
View allArbitrary native code execution in the jahlives openssl_encrypt Python package (all versions before 1.4.0) arises from i
Sandbox escape in the openssl_encrypt Python library (jahlives) before 1.4.0 lets attacker-supplied plugin code break ou
Insecure PRNG import in the jahlives openssl_encrypt Python package (all versions before 1.4.0) places Python's non-cryp
Authentication bypass in the openssl_encrypt Python library (versions before 1.4.0) lets attackers who can tamper with c
Cryptographic shared-secret disclosure in the openssl_encrypt Python library (maintainer 'jahlives') before 1.4.0 lets a
Sandbox escape leading to remote code execution affects openssl_encrypt (the jahlives Python package) in all versions be
Sandbox escape in the openssl_encrypt Python library (jahlives) before 1.4.0 allows attacker-supplied plugins to run wit
Authentication bypass in the jahlives openssl_encrypt library (all versions before 1.4.0) lets remote unauthenticated at
Integrity-protection bypass in the jahlives openssl_encrypt Python library (all versions before 1.4.0) lets an attacker
Weak cryptographic key derivation in the openssl_encrypt Python library (all versions before 1.4.0) stems from its key-n
Arbitrary code execution in jahlives openssl_encrypt before 1.4.0 stems from an inconsistent sandbox: the runtime Plugin
Audit-trail corruption and a security-control race condition in the Python library openssl_encrypt (by jahlives) before
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today