What is the severity of CVE-2022-42160?

CVE-2022-42160 is classified as a high severity vulnerability due to the potential for command injection.

How do I fix CVE-2022-42160?

To fix CVE-2022-42160, update the D-Link COVR firmware to the latest version that addresses this command injection vulnerability.

What devices are affected by CVE-2022-42160?

CVE-2022-42160 affects D-Link COVR 1200, 1202, and 1203 models running firmware version 1.08.

What is a command injection vulnerability in CVE-2022-42160?

In CVE-2022-42160, a command injection vulnerability allows an attacker to execute arbitrary commands on the device through unsafe handling of the system_time_timezone parameter.

Is there a workaround for CVE-2022-42160?

Currently, it is recommended to update the firmware as the best measure for mitigating the risks associated with CVE-2022-42160.

Vulnerability/
CVE-2022-42160

high

8.8

CWE

13/10/2022

3/8/2024

CVE-2022-42160: Command Injection

First published: Thu Oct 13 2022(Updated: )

D-Link COVR 1200,1202,1203 v1.08 was discovered to contain a command injection vulnerability via the system_time_timezone parameter at function SetNTPServerSettings.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Dlink Covr 1203 Firmware	=1.08
Dlink Covr 1203
Dlink Covr 1202 Firmware	=1.08
Dlink Covr 1202
Dlink Covr 1200 Firmware	=1.08
Dlink Covr 1200

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-42160?
CVE-2022-42160 is classified as a high severity vulnerability due to the potential for command injection.
How do I fix CVE-2022-42160?
To fix CVE-2022-42160, update the D-Link COVR firmware to the latest version that addresses this command injection vulnerability.
What devices are affected by CVE-2022-42160?
CVE-2022-42160 affects D-Link COVR 1200, 1202, and 1203 models running firmware version 1.08.
What is a command injection vulnerability in CVE-2022-42160?
In CVE-2022-42160, a command injection vulnerability allows an attacker to execute arbitrary commands on the device through unsafe handling of the system_time_timezone parameter.
Is there a workaround for CVE-2022-42160?
Currently, it is recommended to update the firmware as the best measure for mitigating the risks associated with CVE-2022-42160.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/author
agent/tags
agent/first-publish-date
agent/event
agent/description
agent/source
vendor/dlink
canonical/dlink covr 1203 firmware
version/dlink covr 1203 firmware/1.08
canonical/dlink covr 1203
canonical/dlink covr 1202 firmware
version/dlink covr 1202 firmware/1.08
canonical/dlink covr 1202
canonical/dlink covr 1200 firmware
version/dlink covr 1200 firmware/1.08
canonical/dlink covr 1200

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-42160?
CVE-2022-42160 is classified as a high severity vulnerability due to the potential for command injection.
How do I fix CVE-2022-42160?
To fix CVE-2022-42160, update the D-Link COVR firmware to the latest version that addresses this command injection vulnerability.
What devices are affected by CVE-2022-42160?
CVE-2022-42160 affects D-Link COVR 1200, 1202, and 1203 models running firmware version 1.08.
What is a command injection vulnerability in CVE-2022-42160?
In CVE-2022-42160, a command injection vulnerability allows an attacker to execute arbitrary commands on the device through unsafe handling of the system_time_timezone parameter.
Is there a workaround for CVE-2022-42160?
Currently, it is recommended to update the firmware as the best measure for mitigating the risks associated with CVE-2022-42160.