CVE-2018-6211: Command Injection

Published Jun 20, 2018
·
Updated

On D-Link DIR-620 devices with a certain customized (by ISP) variant of firmware 1.0.3, 1.0.37, 1.3.1, 1.3.3, 1.3.7, 1.4.0, and 2.0.22, OS command injection is possible as a result of incorrect processing of the resbuf parameter to index.cgi.

Affected Software

16 affected components
D-Link Dir-620 Firmware=1.0.3
D-Link Dir-620 Firmware=1.0.37
D-Link Dir-620 Firmware=1.3.1
D-Link Dir-620 Firmware=1.3.3
D-Link Dir-620 Firmware=1.3.7
D-Link Dir-620 Firmware=1.4.0
D-Link Dir-620 Firmware=2.0.22
Dlink Dir-620
All of the following
Any of the following
D-Link Dir-620 Firmware=1.0.3
D-Link Dir-620 Firmware=1.0.37
D-Link Dir-620 Firmware=1.3.1
D-Link Dir-620 Firmware=1.3.3
D-Link Dir-620 Firmware=1.3.7
D-Link Dir-620 Firmware=1.4.0
D-Link Dir-620 Firmware=2.0.22
Dlink Dir-620

Event History

Jun 20, 2018
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Data Sourced
via NVD·04:29 PM
DescriptionSeverityWeaknessAffected Software
Jul 27, 58461
Event
08:11 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-6211?

CVE-2018-6211 has been classified as a critical vulnerability due to the potential for OS command injection that allows unauthorized execution of commands.

2

How do I fix CVE-2018-6211?

To fix CVE-2018-6211, update the D-Link DIR-620 firmware to the latest version provided by the manufacturer.

3

What devices are affected by CVE-2018-6211?

CVE-2018-6211 affects D-Link DIR-620 devices running customized firmware versions 1.0.3, 1.0.37, 1.3.1, 1.3.3, 1.3.7, 1.4.0, and 2.0.22.

4

What kind of attack can be executed through CVE-2018-6211?

CVE-2018-6211 can be exploited to perform OS command injection attacks, allowing attackers to execute arbitrary commands on the affected devices.

5

Is there a workaround for CVE-2018-6211?

There is no known workaround for CVE-2018-6211; upgrading the firmware is the only mitigation available.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203