Tuesday, March 4, 2025
HomeCVE/vulnerabilityCritical Remote Code Execution Bug in Linux Based OpenWrt OS Affects Millions...

Critical Remote Code Execution Bug in Linux Based OpenWrt OS Affects Millions of Network Devices

Published on

SIEM as a Service

Follow Us on Google News

Security researcher uncovered a critical remote code execution vulnerability in OpenWrt operating system that allows attackers to inject the malicious payload on the vulnerable systems.

OpenWrt is a Linux based operating system that is mainly used in embedded devices and network routers to route the network traffic and is installed on millions of devices around the globe.

The RCE bug addressed in the package list parse the logic of OpenWrt’s opkg (Opkg Package Manager) fork let package manager ignore the SHA-256 checksums embedded in the signed repository index which allows an attacker to bypass the integrity checking of downloaded .ipk artifacts.

Guido Vranken, a researcher explained that he found this vulnerability initially by chance when he was preparing a Mayhem task for opkg. Mayhem can serve data either from a file or from a network socket.

” I set up a Mayhem task for opkg install attr (attr is a small OpenWRT package), and implicitly, Mayhem was able to find the remote code execution bug, by detecting the memory bugs in the package unpacker. If OpenWRT’s SHA256 verification had worked as intended, opkg would simply discard the package and not process it, and no segmentation faults would transpire,” researcher said.

OpenWRT RCE Vulnerability Exploitation Process

To exploit this RCE vulnerability, the attacker needs to serve compromised packages from a web server and need to intercept communication between the device and downloads.openwrt.org or the ability to control the DNS server that used by the device to make downloads.openwrt.org point to a web server controlled by the attacker.

In fact, opkg on OpenWrt running as root that allows attackers to gain the write access to the entire file systems and inject the arbitrary code remotely by forged .ipk packages with a malicious payload. 

According to OpenWRT bug fix report “During the attack, a malicious actor needs to pose as MITM, serving a valid and signed package index – e.g. one obtained from downloads.openwrt.org – and one or more forged .ipk packages having the same size as specified in the repository index while an `opkg install` command is invoked on the victim system.”

You can also read the complete technical analysis of this vulnerability here.

The vulnerability has been fixed and assigned CVE-2020-7982 and the users are urged to upgrade to the latest OpenWrt version.

How to Update:

The following commands may be used once all repositories have been updated:

 cd /tmp
 opkg update
 opkg download opkg
 zcat ./opkg-lists/openwrt_base | grep -A10 "Package: opkg" | grep SHA256sum
 sha256sum ./opkg_2020-01-25-c09fe209-1_*.ipk

Also Read:

Critical Vulnerability in ppp Daemon Let Hackers Remotely Exploit the Linux Systems & Gain Root Access

RCE Vulnerability in OpenSMTPD Mail Server Let Hackers Exploit The Linux Systems Remotely

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Hunters International Claims Tata Technologies Cyberattack

Multinational engineering and technology services firm Tata Technologies has reportedly fallen victim to a...

Authorities Seize $31 Million Linked to Crypto Exchange Hack

U.S. authorities announced the seizure of $31 million tied to the 2021 Uranium Finance...

Google, Meta, and Apple Power the World’s Biggest Surveillance System

Imagine a government that tracks your daily movements, monitors your communications, and catalogs your...

Docusnap for Windows Flaw Exposes Sensitive Data to Attackers

A recently disclosed vulnerability in Docusnap's Windows client software (CVE-2025-26849) enables attackers to decrypt...

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

Docusnap for Windows Flaw Exposes Sensitive Data to Attackers

A recently disclosed vulnerability in Docusnap's Windows client software (CVE-2025-26849) enables attackers to decrypt...

CISA Warns of Active Exploitation of Microsoft Windows Win32k Vulnerability

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2018-8639, a decade-old Microsoft Windows...

Update Alert: Google Warns of Critical Android Vulnerabilities Under Exploit

Google’s March 2025 Android Security Bulletin has unveiled two critical vulnerabilities—CVE-2024-43093 and CVE-2024-50302—currently under...