BlackNurse Cybersecurity Alert

background: what is blacknurse?

a recent cybersecurity alert warned that with just a moderately sized laptop and a few simple steps, anyone could bring down a big network firewall machine, using as little as 15 mb/s icmp traffic. this newly discovered vulnerability affects some network equipment from cisco, palo alto and sonicwall, especially if they are not being operated using recommended configurations. because of the suboptimal way in which these devices handle icmp type 3 (destination unreachable) code 3 (port unreachable) packets, an attacker can quickly saturate the devices’ cpu. this is particularly relevant for single cpu devices.

is it relevant to my aws environment?

the short answer is no. there is no indication that the aws networking fabric is affected at all. aws infrastructure is designed for large scale operations (think elb, cloudfront) and is very unlikely to be overwhelmed by this mostly-single-cpu vulnerability.

additionally, because aws has a deny-by-default security group configuration, customer vpcs do not see traffic like this unless an administrator actively changed the configuration to allow the traffic.

now, customers can of course run their own virtual appliances (software) provided by these vendors within their aws instances.

for example, here’s the list of affected cisco devices:

cisco asa 5506, 5515, 5525, 5540 (default settings)

cisco asa 5550 (legacy) and 5515-x (latest generation)

cisco router 897 (unless rate-limited)

these are all physical appliances. the virtual appliance from cisco that customers can install in their aws instance, the cisco adaptive security virtual appliance ( asav) , doesn’t seem to be affected. though there might be some vendor / machine type combination that is vulnerable, it’s unlikely.

how can i be sure?

reading vulnerability reports like these can get security and operations teams worried. using dome9 arc , you can quickly map out your network assets in a public cloud environment and check if any of them are vulnerable to a particular threat. let me show you how.

dome9 arc was designed to be a one-stop security platform for easy management of large public cloud environments. one of the tools in the platform is called policy reports which allows you to quickly generate ad hoc reports of your security policies.

let’s start with the security groups report and add some filters:

protocol: icmp

port: 3 and 256 (port is actually the icmp type. 3 is ‘icmp destination unreachable’ and 256 matches all icmp types)

source: 0.0.0.0/0

you instantly get all relevant security groups that allow icmp type 3 in all you aws accounts and all regions.

still, it is possible that these security groups are just empty or connected to private (non internet accessible) instances. we can generate a similar report, but this time focus on effective security of instances.

let’s go to aws instances report .

again, select the same filters as before but this time also add the following:

has public address: yes

we can verify that there are no public-facing instances which comply with this filter.

the dome9 arc policy reports tool allows administrators to quickly check if any security groups or instances have open ports or permissive policies. it gives admins the means to configure and maintain a closed security posture.