IP cameras have exploded in popularity due to their relatively low cost, wide availability, and ease of installation as surveillance units. The problem is that in isolated cases, the desire for security on one side clashes with the right to privacy on the other, and before starting a deeper conflict, it might be best to explore the possibility of entering your neighbor's surveillance cameras to check their feed. Of course, the idea is to do no harm, and the same procedure applies to detecting other cameras virtually open to the public on the web...
"Privacy vs. security"
The story is probably familiar to some of our readers: A random neighbor decides to install surveillance cameras. One of the cameras seems to be pointing at my property for reasons I can't quite understand. Maybe others would feel more comfortable with that situation... but I don't. However, before filing a complaint or having a more complex discussion, another alternative came up: Enter your neighbor's surveillance cameras and check the content of their feed.
Fortunately, two pre-existing conditions allowed me to succeed without too many surprises: We have the same internet provider, so the IP range in their connections is identical to mine or very similar, and my neighbor knows nothing about computer security. That means the cameras are running with the classic admin/admin or admin/1234, depending on the model. In the end, the problematic camera's feed allowed me to verify that it wasn't pointing at my house, avoiding a crisis.
Now, entering surveillance cameras was useful in my specific case, and the information I'm about to share is for educational purposes only. Once again, the idea is to do no harm, and it also serves as a reminder to review security on any IP device connected to the network.
How to enter surveillance cameras
- The first step is to confirm the IP address assigned by the provider. We won't actually use the exact address, but we need to have an idea of its range. We can use the ipconfig command from the system console, or simply go to Google and type my ip.
- Now that we know the IP address, we need to download a copy of Angry IP Scanner. As its name suggests, it's an open-source utility that allows us to scan IP addresses on both local networks and the Internet, and detect open ports. Although there's a portable edition, I recommend getting the setup, which already includes all its dependencies.
- Before dusting off the Hackerman meme (?), we need to make some adjustments in Angry IP Scanner. On one hand, we need to go to Tools -> Preferences, visit the Ports tab, and add "80,81,90,91,8080,8081,8082" in the configuration section, which represent the most common ports used by IP cameras. On the other hand, we go to Tools -> Finders, and move Detect Web to the active plugins section.
- This is the moment to configure the IP range to scan. The question is, how wide should it be? A range too short will reveal nothing, while processing hundreds of thousands of IP addresses per session doesn't make much sense either. Personally, I usually scan five subnets above and below my IP address. For example, if the address is x.x.45.x, the range to use in Angry IP Scanner goes from x.x.40.0 to x.x.50.255.
- The key to identifying surveillance cameras lies in the description that appears under Detect Web. Many manufacturers place their brand here, such as Hikvision or Dahua, two very popular options on the market. Organizing Angry IP Scanner results is easy: we can click on the Detect Web column and specify Sort by Detect Web.
- The rest is a matter of entering the IP address in a browser and trying to access the camera, hoping that its owner hasn't strengthened security. The classics are admin/admin, admin/1234, admin/12345, and others.
Alternatives?
If scanning IP addresses and checking them manually isn't an option, the first alternative that comes to mind is Shodan. Even with all its restrictions, this search engine for internet-connected devices has impressive firepower. The free version allows a maximum of two pages of results, and you have to create an account to enable search filters, but it's worth making that compromise.
Another possibility is to go to Insecam, with a more traditional search profile. The plan isn't to use Insecam to locate nearby cameras, but to explore open feeds around the world.
In summary: This won't last
Entering surveillance cameras may seem like a malicious activity on the surface, but it doesn't have to be. This helped me avoid an unpleasant conflict (I admit I was very lucky), and at the same time it's useful for any user planning to install their own cameras and verify the level of exposure on each unit.
That said, it's very likely that the practice will lose relevance in the future. The latest camera models already force their users to set strong passwords from the start, thus neutralizing the vulnerability of a classic admin/admin. Good luck!
