Jahlives vulnerabilities
We track 42 vulnerabilities in Jahlives products. 42 are rated high or critical, and none are known to be exploited. The most recent was published on August 27, 2026.
Latest Jahlives vulnerabilities
- 7.5 High severity
openssl_encrypt: Uncontrolled Resource Consumption
openssl_encrypt before 1.4.9 fails to validate KDF cost parameters in encrypted file metadata and keystore headers, allowing attackers to trigger unbounded memory allocation. Attackers can craft malicious encrypted files declaring arbitrarily large Argon2, scr
- 7.8 High severity
openssl_encrypt: Improper Control of Generation of Code
openssl_encrypt before 1.4.9 executes untrusted third-party plugins with insufficient controls: the plugin signature policy defaulted to WARN, so an unsigned/unverifiable non-built-in plugin was compiled and executed in the host process at import time, before
- 7.5 High severity
openssl_encrypt: Inadequate Encryption Strength
openssl_encrypt versions before 1.4.9 use under-parameterized PBKDF2-HMAC-SHA256 with only 100,000 iterations to protect PQC keyfile private keys and 10,000 iterations for dual-encryption file-password verification. Attackers who obtain keyfiles or encrypted f
- 7.0 High severity
openssl_encrypt: Improper Verification of Cryptographic Signature
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 attac
- 9.8 Critical severity
openssl_encrypt before 1.4.9 fails to sanitize the email field of imported identity documents…
openssl_encrypt before 1.4.9 fails to sanitize the email field of imported identity documents, allowing attackers to inject ANSI escape sequences that forge the fingerprint verification line displayed to users. Attackers can deliver a crafted identity bundle t
- 7.5 High severity
openssl_encrypt: Insertion of Sensitive Information into Log File
openssl-encrypt before 1.4.9 fails to redact the file password in its --debug argv dump when the password is supplied via bundled short-option spellings (e.g. -apHunter2) or abbreviated long-option spellings (e.g. --passw). The sanitizer only recognized exact
- 7.5 High severity
openssl_encrypt: Use of Password Hash With Insufficient Computational Effort
openssl_encrypt versions before 1.4.9 contain a weak key derivation vulnerability in the D-Bus CryptoService.EncryptFile handler that uses unstretched SHA-256 instead of Argon2id. Attackers can perform offline password guessing against encrypted files roughly
- 9.8 Critical severity
openssl_encrypt: Insufficient Verification of Data Authenticity
openssl_encrypt before 1.4.9 fails to re-derive and validate fingerprints when loading identities from identity.json, allowing attackers to substitute public keys in identity stores. Attackers can replace legitimate public keys with their own while maintaining
- 9.8 Critical severity
openssl_encrypt: Improper Verification of Cryptographic Signature
openssl_encrypt versions before 1.4.9 use a denylist to identify trusted built-in plugins, allowing unsigned plugins in top-level plugins/ directories and unknown subdirectories to bypass signature verification. Attackers can place malicious unsigned plugins f
- 9.8 Critical severity
openssl_encrypt: Improper Verification of Cryptographic Signature
openssl_encrypt versions before 1.4.9 contain a signature verification vulnerability in gpg_runner.verify_detached that accepts revoked and expired keys by only checking VALIDSIG status without inspecting REVKEYSIG, EXPKEYSIG, or gpg exit codes. Attackers hold
- 7.5 High severity
openssl_encrypt: Allocation of Resources Without Limits or Throttling
openssl_encrypt versions before 1.4.9 fail to properly validate key derivation function costs in crafted files, allowing attackers to trigger unbounded memory and CPU exhaustion during pre-authentication processing. Attackers can supply malicious files with ex
- 8.8 High severity
openssl_encrypt: Improper Neutralization of Special Elements used in an OS Command
openssl_encrypt versions before 1.4.9 contain a shell injection vulnerability in the info command's reconstructed CLI block that interpolates untrusted metadata fields without quoting. Attackers can craft metadata values like pepper_name containing shell comma
- 7.5 High severity
openssl_encrypt: Memory Allocation with Excessive Size Value
openssl_encrypt before 1.4.9 fails to validate the total field from QR JSON payloads before materializing ranges. Attackers can supply crafted QR images with extremely large total values to trigger unbounded memory allocation and cause denial of service throug
- 7.5 High severity
openssl_encrypt: Memory Allocation with Excessive Size Value
openssl_encrypt (pip: openssl-encrypt) versions 1.4.8 and earlier fail to validate the 36-bit STREAMINFO total_samples field of FLAC files before using it to size an allocation (np.random.randint(size=(total_samples, channels))). A ~50-byte crafted FLAC file d
- 7.5 High severity
openssl_encrypt: Cleartext Transmission of Sensitive Information
openssl_encrypt versions before 1.4.9 fail to validate server URLs in login and register_with_email functions, accepting unencrypted http:// URLs and unconfigured hosts. Attackers on the network path can intercept cleartext credentials including client_id, pas
- 7.3 High severity
openssl_encrypt: Improper Link Resolution Before File Access
openssl-encrypt (pip package) before 1.4.9 contains a symlink-following flaw in its verify-usb v2 added-file allowlist scan. The scan enumerated the drive with rglob(), which in CPython does not descend into symlinked directories and treats the symlink as an o
- 7.5 High severity
openssl_encrypt: Use of Password Hash With Insufficient Computational Effort
openssl_encrypt versions before 1.4.9 derive the remote-pepper wrap key using unsalted HKDF-SHA256 or bare SHA-256 of the password, allowing identical keys across all users and files. Attackers with access to wrapped pepper blobs can precompute a single dictio
- 7.5 High severity
openssl_encrypt: Missing Encryption of Sensitive Data
openssl_encrypt versions before 1.4.9 store an unkeyed SHA-256 hash of the plaintext in the cleartext file header metadata. Attackers can read this hash without the password to confirm guessed plaintexts offline or fingerprint identical plaintexts across separ
- 9.8 Critical severity
openssl_encrypt: Improper Verification of Cryptographic Signature
openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption failures trigger fallback to unauthenticated AES-CTR mode. Attackers can modify ciphertext in transit to bypass integrity verification and p
- 9.8 Critical severity
openssl_encrypt versions before 1.4.0 contain a critical vulnerability in pqc.py where KEM…
openssl_encrypt versions before 1.4.0 contain a critical vulnerability in pqc.py where KEM decapsulation failures silently fall back to simulation mode, generating a deterministic shared secret from only 16 bytes of the private key and publicly available encap
- 9.8 Critical severity
openssl_encrypt: Improper Neutralization of Directives in Dynamically Evaluated Code
openssl_encrypt versions before 1.4.0 contain a sandbox escape vulnerability in IsolatedPluginExecutor that exposes Python type objects in restricted exec() builtins. Attackers can traverse the Python class hierarchy via __class__.__mro__.__subclasses__() to a
- 9.8 Critical severity
openssl_encrypt: Protection Mechanism Failure
openssl_encrypt versions before 1.4.0 contain a sandbox escape vulnerability in the DangerousPatternVisitor AST analyzer that fails to detect dunder attribute traversal techniques. Attackers can use __class__, __bases__, __subclasses__(), and __globals__ chain
- 9.8 Critical severity
openssl_encrypt: Protection Mechanism Failure
openssl_encrypt versions before 1.4.0 fail to apply sandbox restrictions in the default process isolation mode for plugin execution. Attackers can execute malicious plugins with unrestricted access to the filesystem, network, subprocess execution, and all Pyth
- 9.8 Critical severity
openssl_encrypt: Improper Authentication
openssl_encrypt before 1.4.0 contains an authentication bypass vulnerability in the verify_api_token function that accepts any non-empty Bearer token string without validation. Attackers can upload arbitrary public keys, enumerate all keys, and revoke keys bel
- 8.8 High severity
openssl_encrypt: Use of Hard-coded Credentials
openssl_encrypt versions before 1.4.0 contain hardcoded default JWT signing secrets in config.py that pass validation checks. Attackers with access to source code can forge valid JWT tokens for any client_id to gain authenticated access to keyserver and teleme
- 7.5 High severity
openssl_encrypt: Use of Hard-coded Credentials
openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry AP
- 9.8 Critical severity
openssl_encrypt: Use of Hard-coded Credentials
openssl_encrypt versions before 1.4.0 contain hardcoded database credentials in standalone server configuration files. Attackers on the same network can access PostgreSQL databases using well-known default credentials to retrieve sensitive data.
- 9.8 Critical severity
openssl_encrypt: Inadequate Encryption Strength
openssl_encrypt versions before 1.4.0 use HKDF with no salt and static info parameter in key normalization functions, reducing entropy extraction and determinism. Attackers can exploit predictable key derivation with identical inputs to weaken cryptographic se
- 7.5 High severity
openssl_encrypt: Use of a Broken or Risky Cryptographic Algorithm
openssl_encrypt versions before 1.4.0 use a non-standard PBKDF2 key derivation construction with iterations=1 per call in an outer loop, creating a KDF whose security properties have not been formally analyzed. Attackers can exploit this weakened key derivatio
- 9.8 Critical severity
openssl_encrypt: Incomplete List of Disallowed Inputs
openssl_encrypt versions before 1.4.0 contain a plugin sandbox bypass vulnerability where the PluginImportGuard blocks a different set of modules than the AST analyzer's DANGEROUS_MODULES set. Attackers can bypass AST analysis through string obfuscation or enc
- 7.5 High severity
openssl_encrypt: External Control of File Name or Path
openssl_encrypt versions before 1.4.0 contain a path traversal vulnerability in the _is_safe_path method where the plugin_id parameter is not sanitized before constructing the plugin config directory path. Attackers can declare a malicious plugin_id containing
- 8.8 High severity
openssl_encrypt: Protection Mechanism Failure
openssl_encrypt versions before 1.4.0 contain a sandbox bypass vulnerability where the plugin sandbox fails to restrict alternative file access methods like pathlib.Path and io.open. Attackers can import pathlib or io modules to read and write arbitrary files,
- 9.1 Critical severity
openssl_encrypt: Insufficient Verification of Data Authenticity
openssl_encrypt versions before 1.4.0 contain an insecure default configuration that trusts the entire RFC 1918 private address space in IntegrityProxyConfig trusted_proxies. Attackers on private networks can forge client certificate headers to bypass mTLS aut
- 9.3 Critical severity
openssl_encrypt: Permissive Cross-domain Security Policy with Untrusted Domains
openssl_encrypt versions before 1.4.0 configure CORS with allow_origins set to wildcard and allow_credentials enabled to true. Attackers can create malicious websites that make authenticated cross-origin requests to the API on behalf of any user who visits the
- 9.8 Critical severity
openssl_encrypt: Use of HTTP Request With Sensitive Query String
openssl_encrypt versions before 1.4.0 accept refresh tokens as URL query parameters in keyserver and telemetry server routes. Attackers can extract tokens from server logs, proxy logs, browser history, and HTTP Referer headers to gain unauthorized access.
- 7.5 High severity
openssl_encrypt: Generation of Error Message Containing Sensitive Information
openssl_encrypt versions before 1.4.0 contain an information disclosure vulnerability in the /ready endpoint that returns full database exception strings to unauthenticated callers. Attackers can trigger database errors to extract sensitive information includi
- 9.8 Critical severity
openssl_encrypt: Allocation of Resources Without Limits or Throttling
openssl_encrypt versions before 1.4.0 use an in-memory rate limiter for TOTP brute-force protection that is not shared across workers and is lost on server restart. Attackers can distribute authentication attempts across multiple server instances or retry imme
- 8.8 High severity
openssl_encrypt: Authorization Bypass Through User-Controlled Key
openssl_encrypt versions before 1.4.0 contain a missing ownership verification vulnerability in the revoke_key method that allows authenticated clients to revoke any other client's key. Attackers can revoke arbitrary keys by providing a valid ML-DSA signature,
- 9.8 Critical severity
openssl_encrypt: Improper Verification of Cryptographic Signature
openssl_encrypt versions before 1.4.0 contain a vulnerability in PublicKeyBundle.from_dict() that creates key bundles from untrusted data without verifying signatures. Attackers can call from_dict() followed by to_identity() without signature verification to e
- 9.8 Critical severity
openssl_encrypt: Insufficient Verification of Data Authenticity
openssl_encrypt versions before 1.4.0 silently skip JSON schema validation when the jsonschema library is not installed, allowing malformed metadata to be accepted. Attackers can remove the jsonschema package or supply unknown metadata format versions to bypas