What is the CVSS score of CVE-2014-3532?

CVE-2014-3532 has a CVSS 2.0 base score of 2.1 (Low). CVSS vector: AV:L/AC:L/Au:N/C:N/I:N/A:P. EPSS exploitation probability: 0.1%.

Is there a patch available for CVE-2014-3532?

Yes, a patch is available for CVE-2014-3532. Update the affected software to the latest version immediately.

Dbus CVE-2014-3532

LOW

Improper Input Validation (CWE-20)

2014-07-19 secalert@redhat.com

Denial Of Service Dbus Opensuse Debian Linux Mageia Solaris

2.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

AV:L/AC:L/Au:N/C:N/I:N/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:L/AC:L/Au:N/C:N/I:N/A:P

Attack Vector

Local

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Jul 19, 2014 - 19:55 cve.org

LOW 2.1

DescriptionCVE.org

dbus 1.3.0 before 1.6.22 and 1.8.x before 1.8.6, when running on Linux 2.6.37-rc4 or later, allows local users to cause a denial of service (system-bus disconnect of other services or applications) by sending a message containing a file descriptor, then exceeding the maximum recursion depth before the initial message is forwarded.

AnalysisAI

dbus 1.3.0 before 1.6.22 and 1.8.x before 1.8.6, when running on Linux 2.6.37-rc4 or later, allows local users to cause a denial of service (system-bus disconnect of other services or applications). Rated low severity (CVSS 2.1), this vulnerability is low attack complexity.

Technical ContextAI

This vulnerability is classified under CWE-20. dbus 1.3.0 before 1.6.22 and 1.8.x before 1.8.6, when running on Linux 2.6.37-rc4 or later, allows local users to cause a denial of service (system-bus disconnect of other services or applications) by sending a message containing a file descriptor, then exceeding the maximum recursion depth before the initial message is forwarded. Affected products include: Freedesktop Dbus, Opensuse, Debian Debian Linux, Mageia, Oracle Solaris. Version information: before 1.6.22.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.