Saturday, January 4, 2025
HomeComputer SecurityMore than 25,000 Linksys Smart Wi-Fi Routers Leaking Sensitive Information to the...

More than 25,000 Linksys Smart Wi-Fi Routers Leaking Sensitive Information to the Public Internet

Published on

SIEM as a Service

A vulnerability with Linksys Smart Wi-Fi routers allows attackers to gain unauthenticated, remote access to the vulnerable router and to access sensitive information.

The vulnerability can be exploited by just knowing the public IP address of the router. It can be exploited simply by just opening the router public IP address in the web browser and from the developer console, move to network and JNAP queries.

By just opening the JNAP queries, the sensitive information will get exposed, and it can be reproduced by sending a request to JNAP endpoint.

- Advertisement - SIEM as a Service

“This sensitive information disclosure vulnerability requires no authentication and can be exploited by a remote attacker with little technical knowledge,” reads BadPackets report.

Following are the sensitive information leak that includes

  • MAC address of every device, including historical one
  • Device name
  • Operating System

In some cases, it includes device type, manufacturer, model number, and description. Other sensitive information such as settings, firewall status, firmware update settings, and DDNS settings are also leaked.

“According to researchers 25,617, Linksys Smart Wi-Fi routers are currently leaking sensitive information to the public internet.”

The leakage pose privacy concerns, by having the extracted details attackers gain access to the home or business networks to launch targeted attacks. Following are the devices affected.

756,565 MAC address was leaked Mursch said, most of the Linksys Smart Wi-Fi routers have not changed the default password, which allows an unauthenticated attacker to gain access to the router. The can also be done by merely querying the following JNAP endpoint.

“Our scans have found thousands of routers are still using the default password and are vulnerable to immediate takeover – if they aren’t already compromised,” Mursch added.

Bad Packet reproduced the issue that fixed before five years, “While CVE-2014-8244 was supposedly patched for this issue, our findings have indicated otherwise,” Mursch said.

Linksys security team determined the issue was “Not applicable /Won’t fix” and subsequently closed.

Related Read

Verizon Fios Router Vulnerabilities Allows Attackers to Gain Complete Control Over the Network

New DNS Hijacking Attack Exploiting DLink Routers to Target Netflix, PayPal, Uber, Gmail Users

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

LegionLoader Abusing Chrome Extensions To Deliver Infostealer Malware

LegionLoader, a C/C++ downloader malware, first seen in 2019, delivers payloads like malicious Chrome...

ASUS Critical Vulnerabilities Let Attackers Execute Arbitrary Commands

In a recent security advisory, ASUS has alerted users to critical vulnerabilities affecting several...

NTT Docomo Hit by DDoS Attack, Services Disrupted for 11 Hours

NTT Docomo, one of Japan’s leading telecommunications and IT service providers, experienced a massive...

Apple Agrees to $95M Settlement Over Siri Privacy Lawsuit

Apple Inc. has agreed to pay $95 million to settle a proposed class-action lawsuit...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

LegionLoader Abusing Chrome Extensions To Deliver Infostealer Malware

LegionLoader, a C/C++ downloader malware, first seen in 2019, delivers payloads like malicious Chrome...

ASUS Critical Vulnerabilities Let Attackers Execute Arbitrary Commands

In a recent security advisory, ASUS has alerted users to critical vulnerabilities affecting several...

NTT Docomo Hit by DDoS Attack, Services Disrupted for 11 Hours

NTT Docomo, one of Japan’s leading telecommunications and IT service providers, experienced a massive...