Friday, February 7, 2025
HomeCVE/vulnerabilityLinksys Router Flaw Let Attackers Perform Command Injection, PoC Released

Linksys Router Flaw Let Attackers Perform Command Injection, PoC Released

Published on

SIEM as a Service

Follow Us on Google News

Linksys routers were discovered with two vulnerabilities: CVE-2024-33788 and CVE-2024-33789.

These vulnerabilities were associated with Command Injection on Linksys routers.

The severity of these vulnerabilities is yet to be categorized. However, a proof-of-concept has been published for these two vulnerabilities.

These vulnerabilities existed in Linksys E5000 routers, which had insufficient validation of user inputs.

Threat actors can exploit this vulnerability and execute unauthorized commands on the affected devices. 

CVE-2024-33788: Command Injection Flaw

This vulnerability exists due to an insufficient validation of input, which arises when registering a device PIN number in the Configure → Wi-Fi → Wi-Fi Protect Config Setting.

Document

Integrate ANY.RUN in Your Company for Effective Malware Analysis

Are you from SOC, Threat Research, or DFIR departments? If so, you can join an online community of 400,000 independent security researchers:

  • Real-time Detection
  • Interactive Malware Analysis
  • Easy to Learn by New Security Team members
  • Get detailed reports with maximum data
  • Set Up Virtual Machine in Linux & all Windows OS Versions
  • Interact with Malware Safely

If you want to test all these features now with completely free access to the sandbox:

This value is provided as input inside the squashfs-root/usr/share/lua/runtime.lua at line number 1561.

At this line of code in the file, there is a pt[”PinCode”], which is not filtered and gets executed directly on the next line where there is a “os.execute(cmd)”.

If the PIN code is provided with a malicious command, it gets executed as output on the router leading to a command injection vulnerability.

CVE-2024-33789: Command Injection through Ping

This is also a command injection vulnerability that exists due to insufficient verification of the input value for the IP or URL address when executing the ping command.

This ping test is present in the router’s TroubleShooting → Diagnostics menu as a means of checking the connectivity.

However, this value is provided as an input to the squashfs-root/usr/share/lua/runtime.lua file at line 491.

This line of code consists of pt[“ipurl”] which is not filtered. Additionally, this value gets executed on the next line which contains the “os.execute(cmd)”.

Hence, providing a malicious value as URL or IP address for the ping command results in command injection vulnerability.

Nevertheless, to exploit these vulnerabilities, a threat actor will need a certain level of permissions on the vulnerable router.

Users of these products are recommended to upgrade to the latest versions to prevent threat actors from exploiting these vulnerabilities.

Is Your Network Under Attack? - Read CISO’s Guide to Avoiding the Next Breach - Download Free Guide

Eswar
Eswar
Eswar is a Cyber security content editor with a passion for creating captivating and informative content. With years of experience under his belt in Cyber Security, he is covering Cyber Security News, technology and other news.

Latest articles

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...

Hackers Leveraging Image & Video Attachments to Deliver Malware

Cybercriminals are increasingly exploiting image and video files to deliver malware, leveraging advanced techniques...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...