Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain local user shell access
-
DeliveryConfirm D-Bus crypto service is active
-
ExploitCraft Properties.Set call with malicious value
-
InstallSend call to system bus without authorization
-
C2Set MaxConcurrentOperations to zero or negative
-
ExecuteDaemon concurrency gate blocks all crypto requests
-
ImpactPersistent root daemon DoS
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires two conditions: (1) the target host must be running openssl_encrypt version 1.4.x before 1.4.9 with the optional D-Bus crypto service installed and running - this service is not present in 1.5.x and its presence in 1.4.x depends on whether the optional component was deployed; and (2) the attacker must possess a local OS user account with access to the D-Bus system bus, which is the default for all local users on Linux systems using systemd/D-Bus. No elevated privileges, no specific group membership, and no special configuration of the attacker's account are required beyond being a logged-in local user. Remote exploitation is not possible without a prior local foothold, as the D-Bus system bus is not exposed over the network. The optional nature of the D-Bus service is the single most important limiting factor: environments that have not installed or enabled it have no exposure regardless of openssl_encrypt version. |
| Impact | The CVSS 4.0 base score of 6.9 (AV:L/AC:L/AT:N/PR:N/UI:N/VA:H) accurately reflects a locally exploitable, low-complexity, high-availability-impact denial-of-service. The local attack vector (AV:L) is the primary risk limiter: the D-Bus system bus is not reachable from the network without a prior foothold, so the realistic threat actor is an insider or a process already running on the host. There is no KEV listing and no EPSS data was provided, and no POC was referenced in the available intelligence, all of which suggest this is not under active or widespread exploitation. The persistence of the impact - the daemon's concurrency gate remains broken across subsequent calls until the property is corrected or the daemon restarted - elevates this beyond a transient nuisance. The narrow applicability (optional D-Bus service, 1.4.x only) further constrains the exposed population. No conflicts between the CVSS vector and the description were identified; both consistently indicate local, low-complexity, no-additional-privilege access as the sole requirement. This is a moderate-priority issue for any operator confirmed to be running the affected version with the optional service active. |
| Exploit ScenarioDerived | A local user with a standard shell account on a host running openssl_encrypt 1.4.x with the D-Bus service active uses dbus-send or gdbus to invoke org.freedesktop.DBus.Properties.Set, passing MaxConcurrentOperations as the property name and -1 or 0 as the value, requiring no elevated privileges or special tooling. The daemon's concurrency gate immediately begins refusing all subsequent cryptographic requests, producing a persistent service outage for any caller relying on the daemon until it is restarted. No public exploit code has been identified at time of analysis, but the attack is reproducible with standard D-Bus utilities available on any Linux desktop or server. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 27, 2026
The optional D-Bus crypto service in jahlives/openssl_encrypt 1.4.x before 1.4.9 exposes org.freedesktop.DBus.Properties.Set without polkit authorization or input validation, enabling any local system-bus user to persistently disable the root daemon. Setting MaxConcurrentOperations to zero or a negative value causes the concurrency gate to reject all subsequent cryptographic requests from the daemon; setting it to an arbitrarily large value or manipulating DefaultTimeout degrades stability in the opposite direction. No public exploit code has been identified at time of analysis, and the flaw is not listed in CISA KEV.
RemediationAI
The primary fix is to upgrade to openssl_encrypt 1.4.9 per the vendor GitHub Security Advisory at https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-7fhx-8rmv-qjj3. A complete elimination of the attack surface is achieved by migrating to the 1.5.x release line, which does not include the D-Bus service at all; operators should verify application compatibility with 1.5.x APIs before migrating. If an immediate upgrade is not possible, the optional D-Bus service can be disabled or removed, which prevents any system-bus exposure but will break applications that depend on the daemon for cryptographic operations - identify and account for those dependents before disabling. As an additional compensating control, D-Bus send policy rules in /etc/dbus-1/system.d/ can be configured to restrict which UIDs or groups may send to the affected service name; this is surgical but requires careful policy authoring to avoid disrupting legitimate callers.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in pypi
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
openssl_encrypt (cpe:2.3:a:jahlives:openssl_encrypt) is a third-party cryptographic daemon by jahlives that, in its 1.4.x branch, optionally registers a service on the D-Bus system bus. The standard org.freedesktop.DBus.Properties.Set interface is intended to be mediated by polkit (PolicyKit), which validates caller identity and privilege level before permitting property writes on the system bus. This implementation omits both the polkit authorization call and any integer-range validation on the incoming value, satisfying CWE-20 (Improper Input Validation). The two exposed properties - MaxConcurrentOperations and DefaultTimeout - govern the concurrency gate and operation timeout for the root daemon process. Because D-Bus system-bus access is available to all local OS users by default, the missing authorization check means any shell account holder can manipulate daemon-wide settings. The service is exclusive to the 1.4.x line and was fully removed in 1.5.x, bounding the attack surface to that specific version range.
Know when Openssl Encrypt gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Local D-Bus system-bus access requires a valid user account (PR:L); no confidentiality or integrity impact; high availability impact via persistent concurrency-gate exhaustion of the root daemon.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
openssl_encrypt 1.4.x before 1.4.9 contains an optional D-Bus crypto service whose org.freedesktop.DBus.Properties.Set method performs neither a polkit authorization check nor value validation. Any local user on the system bus can call Set without authorization and set MaxConcurrentOperations (to 0/negative, causing the concurrency gate to refuse all subsequent operations, or to a huge value removing the limit) or the unbounded DefaultTimeout, resulting in a persistent denial of service of the root daemon. The D-Bus service exists only on the 1.4.x line and was removed in 1.5.x.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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
Fingerprint-verification spoofing in jahlives openssl_encrypt before 1.4.9 lets attackers embed ANSI escape sequences in
Sandbox escape in the openssl_encrypt Python library (jahlives) before 1.4.0 allows attacker-supplied plugins to run wit
Arbitrary code execution in jahlives openssl_encrypt before 1.4.0 stems from an inconsistent sandbox: the runtime Plugin
Authentication bypass in the jahlives openssl_encrypt library (all versions before 1.4.0) lets remote unauthenticated at
Authentication brute-force protection can be bypassed in jahlives openssl_encrypt before 1.4.0 because the TOTP rate lim
Sandbox escape in the openssl_encrypt Python library (jahlives) before 1.4.0 lets attacker-supplied plugin code break ou
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
Arbitrary code execution in openssl_encrypt (the jahlives Python encryption utility) before 1.4.9 allows an attacker-sup
Arbitrary code execution in jahlives openssl_encrypt before 1.4.9 stems from a flawed plugin trust model that uses a den
Sensitive-token exposure in openssl_encrypt (the jahlives Python package, pip 'openssl-encrypt') before 1.4.0 stems from
EUVD-2026-67042
GHSA-jgvp-mwh2-v4m7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB