GARMIN Forerunner 235 up to 8.19 ConnectIQ TVM read/write integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GARMIN Forerunner 235 up to 8.19. It has been rated as critical. This vulnerability affects unknown code of the file read/write of the component ConnectIQ TVM. This manipulation causes integer overflow. This vulnerability is registered as CVE-2020-27484. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability classified as critical was found in GARMIN Forerunner 235 up to 8.19. Affected by this vulnerability is an unknown function of the file read/write of the component ConnectIQ TVM. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was published 11/17/2020 as ATREDIS-2020-0004. The advisory is shared at github.com. This vulnerability is known as CVE-2020-27484. Technical details are known, but no exploit is available.
Upgrading to version 8.20 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.9
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: Integer overflowCWE: CWE-190 / CWE-189
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Forerunner 235 8.20
Timeline
10/21/2020 🔍11/17/2020 🔍
11/17/2020 🔍
12/08/2020 🔍
Sources
Advisory: ATREDIS-2020-0004Status: Confirmed
CVE: CVE-2020-27484 (🔍)
GCVE (CVE): GCVE-0-2020-27484
GCVE (VulDB): GCVE-100-165025
Entry
Created: 11/17/2020 08:23Updated: 12/08/2020 06:48
Changes: 11/17/2020 08:23 (40), 12/08/2020 06:45 (5), 12/08/2020 06:48 (18)
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.