For the second time this year, a flaw in a piece of behind-the-scenes software has set off a scramble across the technology world. In April it was Heartbleed. On September 24, researchers disclosed a bug in a program called bash, and it quickly earned its own nickname: Shellshock.
If you run a Windows office, your first reaction may be "that does not sound like my problem." Your desktops are probably fine. But look around your network closet. Chances are you own several devices that run on Linux or Unix without ever advertising it — and those are where Shellshock lives.
What bash is, and what went wrong
Bash is a "shell," a program that lets people and other programs give commands to a computer by typing text. It has been around since the late 1980s and is standard equipment on Linux, most Unix systems, and Apple's Mac OS X. Many other programs call on bash behind the scenes to get small jobs done.
The flaw is in how bash handles certain settings, called environment variables, that get passed to it. Researchers found that someone could tuck extra commands onto the end of one of those settings, and bash would run them. In some setups, those settings can come straight from the internet — for example, from details a web browser sends to a web server. That means an attacker could, in the worst case, send a specially crafted request to a vulnerable device and make it run commands of their choosing.
The bug appears to have existed for more than twenty years. It is also relatively easy to exploit, and attackers began scanning the internet for vulnerable systems within a day or two of the announcement.
A messy first week
The first patch did not fully fix the problem, and researchers found related issues over the following days. Additional updates followed. That is not unusual for a bug this deep, but it means that a system patched on the first day may need another update. If you patched once and moved on, check again.
With Shellshock, "we patched it" is only true if you patched it more than once.
What is actually at risk
Having bash installed does not automatically make a device exploitable. The danger comes when something exposed to a network passes outside data to bash. The most commonly discussed cases are:
- Linux and Unix web servers, especially those running older-style CGI scripts.
- Macs. OS X includes bash. Apple has said most users are not at risk in a default setup, and it released updates for supported versions of OS X at the end of September. Install them.
- Network storage (NAS) devices. Many are Linux-based with web management pages, and several vendors have issued Shellshock updates.
- Routers, firewalls, and VPN appliances from some vendors. Many small devices use a lighter shell rather than bash and are not affected, but you need to check rather than assume.
- Other embedded gear: security camera recorders, phone systems, printers, and building controls may run Linux inside.
Windows computers are not affected by Shellshock itself, unless someone has installed bash-based tools on them.
The real lesson: devices you forget
Updating Windows desktops is a habit for most offices now. Updating a NAS box that was set up three years ago and never touched since? Not so much. We often see offices where the firewall, storage device, and phone system are all running the firmware they shipped with.
These devices are computers. They have operating systems, they have bugs, and they need updates. They are also often the most exposed things you own, sitting right at the edge of your network or reachable from the internet so staff can get to files and cameras from home. And unlike a laptop, they never pop up a reminder that an update is waiting.
Heartbleed and Shellshock have made this point twice in six months. There will be a next time. The businesses that handle it well are the ones that already know what devices they own and how to update them.
How to get ahead of it
Start by building a simple list of every network-connected device in your office that is not a standard Windows PC:
- What is it, and who makes it?
- What firmware or software version is it running?
- Is it reachable from the internet?
- Who is responsible for updating it?
- Where does the vendor post security updates?
Then go through the list and check each vendor for Shellshock guidance. For anything exposed to the internet that cannot be updated, consider whether it really needs to be exposed. Often a VPN connection for remote staff is safer than opening a device's management page to the whole internet.
What to do now
- Install Apple's bash update on every Mac in the office.
- Check vendor advisories for your NAS, firewall, VPN, and other network devices, and apply updates.
- If you run Linux servers or websites, confirm they have the latest bash patches, not just the first one.
- Close internet access to device management pages that do not need it.
- Build a device inventory and set a schedule to check firmware updates regularly.
Nobody should have to keep track of the security bulletins for every box in the closet on their own. Keeping an inventory, watching for advisories, and applying updates across all your equipment — not just the PCs — is exactly what proactive managed IT services are for. If you are not sure what is on your network or whether it is patched, send us a note at info@pinellasit.com and we will help you find out.
