Guardzilla GZ621W 0.5.1.4 Cloud Communication TK_set_deviceModel_req_handle memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Guardzilla GZ621W 0.5.1.4 and classified as critical. Affected by this issue is the function TK_set_deviceModel_req_handle of the component Cloud Communication. The manipulation results in memory corruption.
This vulnerability is known as CVE-2018-18601. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Guardzilla GZ621W 0.5.1.4. It has been classified as critical. Affected is the function TK_set_deviceModel_req_handle of the component Cloud Communication. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
The TK_set_deviceModel_req_handle function in the cloud communication component in Guardzilla GZ621W devices with firmware 0.5.1.4 has a Buffer Overflow.
The bug was discovered 12/28/2018. The weakness was published 12/31/2018 (Website). The advisory is shared for download at labs.bitdefender.com. This vulnerability is traded as CVE-2018-18601 since 10/23/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-128579 and VDB-128581. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
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: 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/23/2018 🔍12/28/2018 🔍
12/31/2018 🔍
12/31/2018 🔍
01/01/2019 🔍
05/06/2025 🔍
Sources
Advisory: labs.bitdefender.comStatus: Not defined
CVE: CVE-2018-18601 (🔍)
GCVE (CVE): GCVE-0-2018-18601
GCVE (VulDB): GCVE-100-128580
See also: 🔍
Entry
Created: 01/01/2019 12:03Updated: 05/06/2025 21:48
Changes: 01/01/2019 12:03 (58), 04/25/2020 14:14 (1), 05/06/2025 21:48 (16)
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.