tcmu-runner up to 1.2.0 dbus on_unregister_handler null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in tcmu-runner up to 1.2.0. It has been declared as problematic. This affects the function on_unregister_handler of the component dbus. Executing a manipulation can lead to null pointer dereference.
This vulnerability is tracked as CVE-2017-1000200. The attack can be launched remotely. No exploit exists.
It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in tcmu-runner up to 1.2.0. This vulnerability affects the function on_unregister_handler of the component dbus. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:
tcmu-runner version 1.0.5 to 1.2.0 is vulnerable to a dbus triggered NULL pointer dereference in the tcmu-runner daemon's on_unregister_handler() function resulting in denial of service
The bug was discovered 11/16/2017. The weakness was disclosed 11/17/2017 (Website). The advisory is shared for download at github.com. This vulnerability was named CVE-2017-1000200 since 11/16/2017. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 104865 (RHEL 7 : Storage Server (RHSA-2017:3277)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks and running in the context l.
Upgrading eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (104865). The entry VDB-109613 is pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 104865
Nessus Name: RHEL 7 : Storage Server (RHSA-2017:3277)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: github.com
Timeline
11/16/2017 🔍11/16/2017 🔍
11/16/2017 🔍
11/17/2017 🔍
11/18/2017 🔍
11/29/2017 🔍
11/30/2017 🔍
01/10/2023 🔍
Sources
Advisory: RHSA-2017:3277Status: Not defined
CVE: CVE-2017-1000200 (🔍)
GCVE (CVE): GCVE-0-2017-1000200
GCVE (VulDB): GCVE-100-109612
See also: 🔍
Entry
Created: 11/18/2017 08:49Updated: 01/10/2023 17:20
Changes: 11/18/2017 08:49 (65), 12/08/2019 08:22 (3), 01/10/2023 17:20 (5)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.