D-Link has addressed three critical vulnerabilities, tracked as CVE-2024-45694<\/strong><\/a>, CVE-2024-45695<\/strong><\/a>, CVE-2024-45697<\/strong><\/a>
The manufacturer also addressed two high-severity vulnerabilities, tracked as CVE-2024-45696<\/strong><\/a> and CVE-2024-45698<\/strong><\/a>.<\/p>\n\n\n\n
“When D-Link became aware of the reported security issues, we promptly started investigating and developing security patches. The third-party publicly disclosed the problem before the patches were available on our standard 90-day security patch release schedule.” reads the advisory<\/strong><\/a>. “We do not recommend that security researchers act in this manner, as they expose end-users to further risks without patches being available from the manufacturer.”<\/p>\n\n\n\n
Below are the descriptions of the issues addressed by D-Link:<\/p>\n\n\n\n
CVE-2024-45695<\/strong><\/a>\u00a0(9.8 critical): The issue is a stack-based buffer overflow in the web service of certain models of D-Link wireless routers. Unauthenticated remote attackers could exploit this vulnerability to execute arbitrary code on the device. The issue impacts:<\/p>\n\n\n\n
CVE-2024-45696<\/strong><\/a>\u00a0(8.8 high): Certain D-Link router models have hidden functionality that allows attackers to enable the telnet service by sending specific packets to the web service. Once enabled, attackers can log in using hard-coded credentials, but the telnet access is limited to the local network. The issue impacts:<\/p>\n\n\n\n
CVE-2024-45698<\/strong><\/a>\u00a0(8.8 high): Certain D-Link router models have a vulnerability in the telnet service that allows unauthenticated remote attackers to log in using hard-coded credentials and execute arbitrary OS commands due to improper input validation. The issue impacts:<\/p>\n\n\n\n
The company addressed the vulnerabilities in the security bulletin<\/a> in the versions v1.03B01 for COVR-X1870, v1.04B05 for DIR-X4860, and DIR-X5460A1_V1.11B04 for DIR-X5460.<\/p>\n\n\n\n
Follow me on Twitter: @securityaffairs<\/strong><\/a> and Facebook<\/strong><\/a> and Mastodon<\/strong><\/a><\/p>\n\n\n\n
Pierluigi Paganini<\/strong><\/a><\/p>\n\n\n\n
(<\/strong>SecurityAffairs<\/strong><\/a>\u00a0\u2013<\/strong>\u00a0hacking, RCE)\u00a0<\/strong>