Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

9/1/2010
08:30 AM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

Finding Exposed Devices On Your Network

When browsing through SHODAN, it never ceases to amaze me what I can find. How is it that people think it's okay to leave their printers, routers, fiber channel switches, and industrial control systems completely open to the Internet?

When browsing through SHODAN, it never ceases to amaze me what I can find. How is it that people think it's okay to leave their printers, routers, fiber channel switches, and industrial control systems completely open to the Internet?In case you're not sure what SHODAN is, I've mentioned SHODAN a few times in previous articles and blogs like "Gaining A Foothold By Exploiting VxWorks Vulns." It's been referred to as a rainbow table for Internet-accessible computers because it provides a searchable index of service banners retrieved from HTTP, HTTPS, FTP, SSH, and telnet services on the Internet without the need to do any of your own scanning.

When I was looking at the VxWorks vulnerability, I found vulnerable printers, network switches, fiber channel switches, and industrial control systems (or SCADA) equipment through some simple searches that are mentioned in this blog.

So I'm left wondering who thought it was a good idea to put these devices on the Internet without some sort of protection in place. Is there no change management procedures at these organizations where someone should be monitoring what's taking place on the network? Surely someone has to provision the public IP for use for the devices. Why aren't they asking what the IP will be used for and if the device is being locked down?

Sure, you can use SHODAN to check your netblocks for exposed devices that you might not be aware of, but why not be a little more proactive? Isn't proactive security better than reactive security? Or more to the point, wouldn't you rather find out about a new exposed device on you network before an attacker does?

There are a couple ways to go about this. The first is setting up some simple network scans using Nmap. It could be done daily or weekly, but I wouldn't recommend going as long as a month in between scans. Be sure to set up the scans to save the output to the Nmap XML format. Once you have more than one scan, you can use the Ndiff utility to compare the two scans and determine if there are any state changes for hosts, ports, service versions, operating systems, and the output of scripts.

The Nmap route is cheap and easy to implement, but if you have a nice netflow analysis solution like Lancope's StealthWatch, it can be done even easier. All of the netflow monitoring tools I've seen have an alert option that will notify admins when a new host is seen communicating on the network. I've also seen alerts for when a host begins acting as a server for the first time. For example, if a host is on the network and begins accepting and responding to requests on TCP port 443 for the first time, admins will receive an alert.

Security teams are often the last ones to know when new systems are brought online, but they don't have to be. Using the tools above, security can know when new systems show up on the network and take appropriate actions such as a vulnerability scan, and confirm that the device is authorized and not some rogue wireless router an employee decided to plug in so they could use their new iPad.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31769
PUBLISHED: 2021-06-21
MyQ Server in MyQ X Smart before 8.2 allows remote code execution by unprivileged users because administrative session data can be read in the %PROGRAMFILES%\MyQ\PHP\Sessions directory. The "Select server file" feature is only intended for administrators but actually does not require autho...
CVE-2020-20469
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a SQL injection vulnerability. The vulnerability stems from the log_edit.php files failing to filter the csa_to_user parameter, remote attackers can exploit the vulnerability to obtain database sensitive information.
CVE-2020-20470
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has web site physical path leakage vulnerability.
CVE-2020-20471
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has an unauthorized access vulnerability in default_user_edit.php, remote attackers can exploit this vulnerability to escalate to admin privileges.
CVE-2020-20472
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a sensitive information disclosure vulnerability. The if_get_addbook.php file does not have an authentication operation. Remote attackers can obtain username information for all users of the current site.