Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.483% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zte
Zte zxhn E1600 Firmware Zte zxhn E2603 Firmware Zte zxhn E2615 Firmware Zte zxhn E2618 Firmware Zte zxhn E500 Firmware Zte zxhn H108n Firmware Zte zxhn H168a Firmware Zte zxhn H168n Firmware Zte zxhn H338a Firmware Zte zxhn Z500 Firmware |
|
| Weaknesses | CWE-121 | |
| CPEs | cpe:2.3:o:zte:zxhn_e1600_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_e2603_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_e2615_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_e2618_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_e500_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_h108n_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_h168a_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_h168n_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_h338a_firmware:*:*:*:*:*:*:*:* cpe:2.3:o:zte:zxhn_z500_firmware:*:*:*:*:*:*:*:* |
|
| Vendors & Products |
Zte
Zte zxhn E1600 Firmware Zte zxhn E2603 Firmware Zte zxhn E2615 Firmware Zte zxhn E2618 Firmware Zte zxhn E500 Firmware Zte zxhn H108n Firmware Zte zxhn H168a Firmware Zte zxhn H168n Firmware Zte zxhn H338a Firmware Zte zxhn Z500 Firmware |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The HTTPD binary in multiple ZTE routers has a stack-based buffer overflow vulnerability in check_data_integrity function. This function is responsible for validating the checksum of data in post request. The checksum is sent encrypted in the request, the function decrypts it and stores the checksum on the stack without validating it. An unauthenticated attacker can get RCE as root by exploiting this vulnerability. | |
| References |
|