GoPro gpmf-parser up to 1.2.0 GPMF_parser.c GPMF_ScaledData divide by zero
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in GoPro gpmf-parser up to 1.2.0. This vulnerability affects the function GPMF_ScaledData of the file GPMF_parser.c. This manipulation causes divide by zero.
This vulnerability is handled as CVE-2018-18190. It is possible to launch the attack on the local host. There is not any exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in GoPro gpmf-parser up to 1.2.0. It has been declared as problematic. Affected by this vulnerability is the function GPMF_ScaledData of the file GPMF_parser.c. The manipulation with an unknown input leads to a divide by zero vulnerability. The CWE definition for the vulnerability is CWE-369. The product divides a value by zero. As an impact it is known to affect availability. The summary by CVE is:
An issue was discovered in GoPro gpmf-parser before 1.2.1. There is a divide-by-zero error in GPMF_ScaledData in GPMF_parser.c.
The bug was discovered 10/09/2018. The weakness was released 10/09/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-18190 since 10/09/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 1.2.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: Divide by zeroCWE: CWE-369 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: gpmf-parser 1.2.1
Timeline
10/09/2018 🔍10/09/2018 🔍
10/09/2018 🔍
10/09/2018 🔍
10/10/2018 🔍
05/23/2023 🔍
Sources
Product: github.comAdvisory: 41
Status: Not defined
CVE: CVE-2018-18190 (🔍)
GCVE (CVE): GCVE-0-2018-18190
GCVE (VulDB): GCVE-100-125161
Entry
Created: 10/10/2018 13:15Updated: 05/23/2023 19:24
Changes: 10/10/2018 13:15 (58), 04/01/2020 11:25 (1), 05/23/2023 19:24 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.