First published: Thu Aug 25 2016(Updated: )
Stack-based buffer overflow in dws/api/Login on D-Link DIR-850L B1 2.07 before 2.07WWB05, DIR-817 Ax, DIR-818LW Bx before 2.05b03beta03, DIR-822 C1 3.01 before 3.01WWb02, DIR-823 A1 1.00 before 1.00WWb05, DIR-895L A1 1.11 before 1.11WWb04, DIR-890L A1 1.09 before 1.09b14, DIR-885L A1 1.11 before 1.11WWb07, DIR-880L A1 1.07 before 1.07WWb08, DIR-868L B1 2.03 before 2.03WWb01, and DIR-868L C1 3.00 before 3.00WWb01 devices allows remote attackers to execute arbitrary code via a long session cookie.
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
D-Link DIR-868L Firmware | <=2.03 | |
D-Link DIR-868LW | =b1 | |
D-Link DIR-822 firmware | =3.01 | |
D-Link DIR-822 | =a1 | |
D-Link DIR-880L A1 Firmware | <=1.07 | |
D-Link DIR-880L Firmware | =a1 | |
D-Link DIR-850L | <=2.07 | |
D-Link DIR-850L Firmware | =b1 | |
D-Link DIR-895L/R Firmware | <=1.11 | |
D-Link DIR-895L Firmware | =a1 | |
D-Link DIR-817L Firmware | <=jul.2016 | |
D-Link DIR-817L | =ax | |
D-Link DIR-818L Firmware | <=2.05 | |
D-Link DIR-818L | =ax | |
D-Link DIR-890L A1 Firmware | <=1.09 | |
D-Link DIR-890L Firmware | =a1 | |
D-Link DIR-823 A1 Firmware | <=1.00 | |
D-Link DIR-823 Firmware | =a1 | |
D-Link DIR-885L/R Firmware | <=1.11 | |
Dlink DIR-885L MFC | =a1 | |
D-Link DIR-868L Firmware | <=3.00 | |
D-Link DIR-868LW | =c1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5681 is classified as a high severity vulnerability due to its potential for remote code execution through stack-based buffer overflow.
To fix CVE-2016-5681, update your D-Link device firmware to the latest version provided by D-Link which addresses this vulnerability.
CVE-2016-5681 affects several D-Link devices including DIR-850L, DIR-880L, DIR-890L, DIR-895L, DIR-817L, DIR-818L, DIR-822, and DIR-823 models running specific firmware versions.
Yes, CVE-2016-5681 can potentially lead to unauthorized access and data breaches due to its nature of allowing remote execution of code.
The best course of action for CVE-2016-5681 is to promptly apply firmware updates, as no reliable workaround is available.