VulnerabilityPublished 9 Oct 2022Updated 9 Jun 2025

CVE-2022-42010: D-Bus · Improper Verification of Cryptographic Signature

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 1.16.0 : update affected systems when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.16.0, 1.15.2, 1.14.4 +2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Oct 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Debiandebian/dbus`pkg:deb/debian/dbus`Other threats	Affected <1.12.24 >=1.13.0 <1.14.0 <1.14.4 >=1.15.0 <1.16.0 <1.15.2	Fixed in 1.12.24 1.14.0 1.14.4 1.16.0 1.15.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2022-42010, European organizations should take the following specific actions: 1) Identify all systems running vulnerable versions of D-Bus by auditing installed package versions across Linux and Unix-like environments. 3) Restrict and monitor authenticated access to systems using D-Bus to minimize the risk of malicious message injection, including enforcing strict access controls and using multi-factor authentication where possible. 4) Implement network segmentation and firewall rules to limit exposure of systems running dbus-daemon to untrusted networks or users. 5) Deploy runtime monitoring and anomaly detection tools to identify unusual dbus-daemon crashes or message patterns indicative of exploitation attempts. 6) Establish incident response procedures to quickly recover from potential DoS events caused by this vulnerability, including automated service restarts and failover mechanisms. 7) Educate system administrators and security teams about the vulnerability and the importance of timely patching and access control enforcement. These measures go beyond generic advice by focusing on access restriction, proactive monitoring, and operational readiness to handle service disruptions.

Description

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash when receiving a message with certain invalid type signatures.

Impact

For European organizations, the impact of CVE-2022-42010 can be significant, especially for those relying heavily on Linux-based infrastructure where D-Bus is integral to system and application communication. The denial of service caused by crashing dbus-daemon can disrupt critical services, automated processes, and system management tasks, potentially leading to downtime in servers, workstations, or embedded systems. This can affect sectors such as finance, healthcare, manufacturing, and public administration, where system availability is crucial. Additionally, environments with multi-tenant or shared systems could see broader impact if an attacker exploits this vulnerability to disrupt multiple services simultaneously. Although the vulnerability requires authenticated access, insider threats or compromised accounts could be leveraged to trigger the DoS. The lack of impact on confidentiality and integrity reduces the risk of data breaches, but availability disruptions can still cause operational delays, financial losses, and reputational damage. Given the medium severity and the nature of the vulnerability, organizations should prioritize patching and monitoring to prevent exploitation, especially in critical infrastructure and production environments.

CWE-347Improper Verification of Cryptographic Signature (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
Attack patterns
Padding Oracle Crypto Attack (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 20:32 UTC

WeaknessesCWE-347

Technical details

References

Community reviews

Related threats