Wednesday, January 1, 2025
HomeDDOSBlack Nurse attack: Will a single laptop bring down Servers/Routers

Black Nurse attack: Will a single laptop bring down Servers/Routers

Published on

SIEM as a Service

Black Nurse attack is a new-threat emerging on it’s horizon, it can be launched from a single laptop which is capable of bringing server/firewalls to their knees.

ICMP is an very commonly used protocol to identify live hosts, It is used by network devices like switches, Routers for sending error messages and operational information’s, for instance service is not available OR the host/server is reachable.You find the most detailed and types of ICMP code’s here.

Black Nurse attack mechanism

Most ICMP attacks based on Type 8 Code 0 also called ping flood attack. Blacknurse is based on ICMP with Type 3 Code 3 packets.We know that when a user has allowed ICMP Type 3 Code 3 to outside interfaces, the BlackNurse attack becomes highly effective even at low bandwidth.

- Advertisement - SIEM as a Service
black1

This attack will be more effective even with the Low bandwidth(15-18Mbit/s). When the attack in progress the users from the LAN network will not able to send/receive over the Internet. All the firewalls/router will recover will recover once the attack stops.

Different firewalls would have different implementation for handling this type of attack,this even applied to customers with large internet uplinks and large enterprise firewalls in place.

Evaluating the Risk

You can implement the test with WAN area of the firewall and at the time of attack try to surf some pages in and out of Internet.The tests also showed that a single attacking machine running hping3 could, on its own, produce enough ICMP type 3 code 3 packets to consume pretty much all the firewall’s resources.

hping3 –icmp -C 3 -K 3 -i u200 [target]

hping3 –icmp -C 3 -K 3 –flood [target]

Here -i u200 orders hping3 to send packets every 200microseconds and few minutes later they upped the packet rate, by using the “–flood” argument.

Detection/Affected products

  • Cisco ASA 5506, 5515, 5525 (default settings)
  • Cisco ASA 5550 (legacy) and 5515-X (latest generation)
  • Cisco Router 897 (can be mitigated)
  • SonicWall (misconfiguration can be changed and mitigated)
  • Some unverified Palo Alto
  • Zyxel NWA3560-N (wireless attack from LAN side)
  • Zyxel Zywall USG50

Impact

Based on the research, this vulnerability or misconfiguration of some firewalls is easy to misuse.Impact can be high for those that allow ICMP to the firewall’s outside interface. Having high bandwidth is no guarantee  that this DOS/DDOS attack will not work.Impact can be different from network to network depends on what the network is covering. It’s recommend to test your network.

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

DrayTek Devices Vulnerability Let Attackers Arbitrary Commands Remotely

The DrayTek Gateway devices, more specifically the Vigor2960 and Vigor300B models, are susceptible to...

New Stealthy Malware Leveraging SSH Over TOR Attacking Ukrainian Military

Researchers recently discovered a malicious campaign targeting Ukrainian military personnel through fake "Army+" application...

CISA Warns of Palo Alto Networks PAN-OS Vulnerability Exploited in Wild

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued a high-priority alert on...

US Treasury Department Breach, Hackers Accessed Workstations

The Biden administration confirmed that a Chinese state-sponsored hacking group breached the U.S. Treasury...

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

Over 300,000 Prometheus Servers Vulnerable to DoS Attacks Due to RepoJacking Exploit

The research identified vulnerabilities in Prometheus, including information disclosure from exposed servers, DoS risks...

Europol Shutsdown 27 DDoS Service Provider Platforms

In a major international operation codenamed “PowerOFF,” Europol, collaborating with law enforcement agencies across...

Hackers Exploit Docker Remote API Servers To Inject Gafgyt Malware

Attackers are exploiting publicly exposed Docker Remote API servers to deploy Gafgyt malware by...