| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in gpsd and microjson. Affected by this issue is some unknown functionality of the component JSON Data Handler. The manipulation leads to memory corruption. This vulnerability is listed as CVE-2018-17937. The attack must be carried out from within the local network. There is no available exploit. It is recommended to apply restrictive firewalling.
Details
A vulnerability was found in gpsd and microjson (affected version not known) and classified as critical. This issue affects some unknown functionality of the component JSON Data Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
gpsd versions 2.90 to 3.17 and microjson versions 1.0 to 1.3, an open source project, allow a stack-based buffer overflow, which may allow remote attackers to execute arbitrary code on embedded platforms via traffic on Port 2947/TCP or crafted JSON inputs.
The bug was discovered 02/14/2019. The weakness was presented 03/13/2019 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2018-17937 since 10/02/2018. The attack can only be initiated within the local network. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 27 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176765 (Debian Security Update for gpsd (DLA 1738-1)).
Addressing this vulnerability is possible by firewalling tcp/2947.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.5
VulDB Base Score: 6.3
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Firewalling: 🔍
Timeline
10/02/2018 🔍02/14/2019 🔍
03/13/2019 🔍
03/14/2019 🔍
08/01/2023 🔍
Sources
Advisory: DLA 1738-1⛔Status: Not defined
CVE: CVE-2018-17937 (🔍)
GCVE (CVE): GCVE-0-2018-17937
GCVE (VulDB): GCVE-100-131693
SecurityFocus: 107029
Entry
Created: 03/14/2019 07:13Updated: 08/01/2023 08:58
Changes: 03/14/2019 07:13 (56), 05/16/2020 11:53 (2), 08/01/2023 08:58 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.