NMAPing IP Cameras

By: Ethan Ace, Published on Mar 05, 2015

The Hikvision hack has increased security concerns.

Indeed, most users do not know whether they are vulnerable or not, which ports of their systems are open, and what services they may be running, leaving them potentially vulnerable.

NMAP, a common security network tool, can be used to check for some vulnerabilities, but is not used as much as it should be.

In this test, we show how it may be used to check your cameras and systems for potential security problems, as well as discovering IP cameras and finding non-standard ports being used for video transmission.

Then we run it on cameras from:

  • Arecont Vision
  • Avigilon
  • Axis
  • Bosch
  • Dahua
  • Hikvision

The test shows which cameras allow the most open ports and the greatest potential security risks.

*** ********* **** *** increased ******** ********.

******, **** ***** ** not **** ******* **** are ********** ** ***, which ***** ** ***** systems *** ****, *** what ******** **** *** be *******, ******* **** potentially **********.

****, * ****** ******** network ****, *** ** used ** ***** *** some ***************, *** ** not **** ** **** as ** ****** **.

** **** ****, ** show *** ** *** be **** ** ***** your ******* *** ******* for ********* ******** ********, as **** ** *********** IP ******* *** ******* non-standard ***** ***** **** for ***** ************.

**** ** *** ** on ******* ****:

  • ******* ******
  • ********
  • ****
  • *****
  • *****
  • *********

*** **** ***** ***** cameras ***** *** **** open ***** *** *** greatest ********* ******** *****.

[***************]

Using ****

**** ** * **** and **** ****** ******* used *** ******* ******** and ******** ********. *** most ********* *** ** IP ************ ** *********** which ***** ** * given ****** *** ****** and ****. ***** *** be *** ****** * single ****** ** ********, even ** ****** ******.

**** ****** ** * command **** ******* **** many ******* ******** *** operators. *** ******* ** run * **** **** of *** *** *****, for *******, ***** **** this:

**** -* *-***** -** -A -* ***.**.***.***

*******, ********* ********** *** available ***** ******** *** and *** ****** **** options ** * ******** menu, **** ********, ***** **** ** Mac ***:

**** ***** ******* *** basic ********* ** **** using *** ****** ***.

Scan *******

*** ******* ** * scan ****, ********* ** which ** ****, **** some ***** * ***** list ** **** ***** while ****** *** ********, multi-page ******* ******* ******* types *** ***********.

**** ******* ***** * quick **** ** * single ****** (***** *********):

******** **** *.** ( http://nmap.org ) ** ****-**-** 16:47 *** **** **** report *** ***.**.***.*** **** is ** (*.***** *******). Not *****: *** ****** ports **** ***** ******* 23/tcp **** ****** **/*** open **** ***/*** **** rtsp ****/*** **** ****** 5000/tcp **** **** *****/*** open ******* *** *******: 90:02:A9:08:14:8A (******** ***** ********** Co.) **** ****: * IP ******* (* **** up) ******* ** *.** seconds

**** ******* ***** *** same ******, **** ** intense **** ** *** TCP *****. **** **** this **** ** **** complex, ******* ******** ******* information **** *********, **** as ******* *** ** versions. ***** **** ********** scans **** ************* ****** than ******* *****, ** to **** ** **** or ****, ****** *-** seconds.

******** ******* *********** *** be **** ** *** intense **** ** *** telnet **** *****, ***** indicates "******* *******" ** the ****** ** *** by *** ******. **** this ***********, ********* *** more ****** ****** *** ways ** ******* ***** open *****. ******* ****** *** "******* telnetd *******", *** *******, ******* many *******, ********* ******** instructions.

Common ****** *****

** ******* ** ******* from * ****** ************* to *** *** **** differed. **** ***** *** running ******** ****** ******, with **** ******* **** two ** ***** ******* ports **** (****, *****, RTSP), ***** ****** ****** 10 ** **** *** various ********, ********* ******, SSH, ****, ******** **** streams, *** ****.

***** ** * ********* of ******* **** ****** manufacturers, ******* **** ******* open ***** (**** *** RTSP) ** ********, ** well ** ******** ** whether ***** ***** ***** be ****** *** *** camera's *** *********:

******* ****** ********

******* ****** ******* **** only **** *** **** ports. **** **** **** probes (-** ** *** command ****) **** ** disabled ** ***** ** scan ******* ******* ** all, ** **** ***** the **** ** ****** first.

**/*** **** ****
***/*** **** ****
****/*** **** ****-*****

******** *.**-***-***

** **** *******, ********'* cameras **** **** *** bare ******* ** *****, HTTP, *****, *** ****.

**/*** **** ****
***/*** **** *****
***/*** **** ****

**** *****

*** *****, ** **** as *** ***** **** cameras ** ******, *** four ***** ****, *** common **** *** **** ports, ** **** ** FTP (**** ** ****** firmware, **** ************, ***. to *** ******), *** UPnP, ******* ** **** 49152. *** *** **** may **** ** ****** off ** ******* ********.

**/*** **** ***
**/*** **** ****
***/*** **** ****
*****/*** **** *******

***** ***-*****

***** ******* ******* ****** typical **** *** **** ports, ** **** ** iSCSI, ***** **** *** for **** *******, ******, and **** ** *****. Telnet *** **** *** be ****** *** *** web *********.

**/*** **** ******
**/*** **** ****
***/*** **** *****
***/*** **** ****
****/*** **** *****
*****/*** **** *******

***** ***-********

***** ******* **** *** following ***** ** *******. Only **** *** ** disabled. ***** ** ** option ** ***** ***** ports.

**/*** **** ******
**/*** **** ****
***/*** **** ****
****/*** **** ******
****/*** **** ****
*****/*** **** *******

****** ****** ****

****** **** ** ** closed ** ***** ******* in ******** *.*** *** up, **** ** ****** to ****** ** ** the ******'* *** *********. Other **** ***** ****** unchanged. ****** *** ********** used ** ****** ***** cameras ** * ***** scale ****** (***:****** ***** ******* ***** Massive ***** ******).

**/*** **** ****
***/*** **** ****
****/*** **** ******
****/*** **** ****
*****/*** **** *******

********* **-*******-*

** **** ******, ******** ports *** **** *** services ***** **** **** and ****. **** ***, 49152 ***** ** ****** by ******* *** ****.

**/*** **** ***
**/*** **** ******
**/*** **** ****
***/*** **** *****
***/*** **** ****
****/*** **** ****-********
****/*** **** ****-***
****/*** **** ********
*****/*** **** *******

****** ****** ****

********* **************** * ***** ********* ** ******** **** released *** ******** (*** test *******). ** ******* of ******* ** **** ports ** ***** ***** between * ****** ******* 5.3.0 ******** *** *** running *.*.*, **** ****** closed (** **** ** ftp *** *****, ***** are *** ******** ** default).

********* **-********-** ***

** **** ******* ******** Hikvision ****, ******* ******** open ***** ** ******** to ******* **** ********. We ***** ** *** to ***** ***** ***** via ********.

**/*** **** ****
****/*** **** ****-***
****/*** **** ***
****/*** **** *******
*****/*** **** *******
*****/*** **** *******

***** *************

**** ********, ***** ************* such ** ****, *********, and ***** ****** **** HTTP *** **** ***** by *******, **** **** also ********* **** (******** via ********).

Other ****

***** *** *** ***** practical **** *** **** in ************:

** ********

**** *** **** ** used ** **** * subnet ** *** ***** devices *** ** (********** to ****) ** ***. These ******* *** ******* to ******** ***** **** as***** ** ***************** ** *******. ***** ** ***** results, ***** *** ****** one ** **** ******* to ******* ****** ***** upon.

** ***** *******, **** also *********** ******* ** ***, *********** *** ************ of **** ****** ***** possible.

******* ***-******** *****

** **** *******, ***-******** ports *** ** **** for **** ******* ** ONVIF. **** ** **** often **** ***-**** ******, though ****** **********, ** at ***. ***** **** allows ***** ** ********* which ***** *** ** use *** ***** ********.

*** *******, ***** ******* port **, *** ******* camera **** ******** ***-**** ************ *** ******* ** any ***. **** *******, the ****** ******* ******* ports *** ****, ****, and ******, *** *** unusual ****: **** *** 8999. ******* * ****** scan ** **** ***** ports ***** ** **** port **** ** **** and ******* ****, *** protocol **** ** *****.

**** ***** *******
****/*** **** **** ***** soap *.*

****** *** ****** ***** ONVIF *** **** ****, it ************ ******** ** VMSes.

Comments (10)

This is a great article. Thank you.

This is a great article. I was not aware of this tool. Thank you for posting.

This article does a great service, thanks.

One thing that's been nagging at me in these various Hikvision discussions recently.. I get the feeling many people here are thinking about Hikvision cameras and what vulnerabilities may be present. Maybe because when they hear Hikvision they think "camera."

In Hikvision's statement from last year they do admit some vulnerabilities in their cameras. They talk about the default password, and telnet being available, and released new camera firmware at that time to disable telnet and enforce better password policy. In the same statement they talk about their DVR firmware--also discussing default passwords, telnet, and password policy. (I'm talking about this statement: https://ipvm-uploads.s3.amazonaws.com/uploads/8341/3f4f/HikvisionOutlinesUpdatesToSurveillanceProducts.pdf )

Of course, default passwords, weak passwords, and telnet (because it exposes passwords in the clear) could all be used to gain user or admin level access to a device. But in some cases that vulnerability may be of limited risk due to the additional need to elevate ones permissions in order to further exploit the device/network. I.e, "you can log in and change the resolution of my camera, big deal."

But the other discussions surrounding actual Hikvision exploits talk about their DVRs in particular and the RTSP buffer overflow issue (wired article: http://www.wired.com/2014/04/hikvision/ , SecurityWeek article: http://www.securityweek.com/multiple-vulnerabilities-found-hikvision-dvr-devices ). The DVRs appear to be running a linux (/dev/watchdog). And the exploits are shown to provide "full control" of the device.

I am just pointing this out because I've always felt that DVRs/NVRs are the real high risk components in a surveillance network. They tend to be more powerful devices, already hold all the video (if protecting video is your concern), tend to run a fuller linux (or Windows) command set if not running a full commodity OS and thus are at greater risk of rootkit, require more open protocol implementations for interoperability and integration, and may be based on a commodity hardware platform rather than the more exotic SoCs used in many cameras.

DVRs are big juicy targets, and are harder to protect than cameras. I suspect that's why Hikivision is in the doghouse today.

Hi John, thank you for your very helpful article. For those cameras which do not offer ways to disable unnecssary ports, do you think adding rules to the firewall, to block ports on the cameras and NVR's, would be an adequate solution? Thank you.

If your system is behind a NAT device, like, well, pretty much every home router, there shouldn't be any special considerations needed to prevent access to devices from the Internet at large - ports must still be forwarded from the WAN interface to the devices' LAN addresses. Ports don't need to blocked, really, they just need to NOT be forwarded to devices on the LAN.

Where there IS a concern is with devices using UPnP to map their own port forwarding, something many devices AND routers now have enabled by default. If manufacturers left this option disabled out-of-the-box it would probably eliminate a lot of the concern, as it would then take specific action by the operator or installer to either enable UPnP, or forward those ports manually, to even make access to the DVR/NVR/cameras possible.

Of course, if an outside has direct access to your LAN, well... you have bigger things to worry about that whether they can snoop on your lunchroom camera.

John, this is a great article. I would add one warning to it. If you run an Nmap scan on a network with older IP cameras, say cameras made before 2010, it is possible that some cameras would go offline. This wouldn't happen with Axis, Bosch, Panasonic or Sony cameras for example, but it could with popular low-cost competors. I've written about this twice in my Convergence Q&A column, as the experiences with this were classified as "incidents". In one case, relayed to me by a consulting colleague of mine, over 100 network cameras were taken offline when an IT tech did an Nmap scan. This was a deployment done in 2004. They were not PoE cameras. People had to be sent out to the camera locations to manually recycle their power. Not a fun day. I wrote about it again a couple of years later when a Nessus scan took an entire network of IP cameras offline, and it required more than just power cycling to get them back on (I don't know the technical details).

Because in each of these cases it was a practice the IT departments to periodically scan all devices on their network, ths was taken into account by adding the IP addresses of the cameras to the Do Not Scan list.

Performing both an Nmap scan and a Nessus scan - whether or not the cameras will be connected to a larger corporate network - should be a standard test before finalizing any network camera deployment.

I have had integrator techs tell me that they don't need to do that, because their cameras are on a physically independent network. However, you have to anticipate that the isolated network status could change in the future. Additionally, for deployments with older cameras that are vulnerable in this way, you have to remember that this is a security vulnerability, becasue attackers gaining access to the video network don't need a password or special skills to take the network down. They can just run the default scan.

I believe that two manufacturers involved in these incidents have since upgraded the firmware for their cameras to eliminate this vulnerabilty or fixed it in a replacement model. But it is common for deployed cameras not to get their firmware upgraded once everything is working well.

Standalone video networks still need to have securty measures in place, regardless of the age of the cameras, so that traffic from non-approved devices (such as an attacker's laptop) can't flood the network.

Nice. Sheds some light on Rodney's 'knockdown scans'.

Wow, this takes me back to the days of crashing co-workers' NT machines with the ol' "ping of death". Good times!

So I've been NMAPping the guest wifi here at Starbucks... still hasn't found anything, including my phone or the guy's laptop at the next table, but it's only 5% into the SYN scan. Neat tool, very inclusive. I've been using Advanced IP Scanner (from www.radmin.com) for a long time and will probably stick to that for finding stray network devices, like when my managed switch doesn't show up on the DHCP server, but this is definitely getting added to my toolbox for those times soemthing stonger is needed.

Very Usefull article.

Let's add that with some vendors, rtsp ports by default (factory settings) don't require credentials....so .... you can first sniff the network, get the IPs and then access video without passwords with Vlc. IF you can see the security from inside, then a physical introduction becomes very easy.. yahoo!

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports on ONVIF

Last Chance - Camera Course Summer 2019 on Jul 11, 2019
Last day to register is Thursday, July 11, 2019. This is the only independent surveillance camera course, based on in-depth product and technology...
Poor OSDP Usage Statistics 2019 on Jul 09, 2019
OSDP certainly offers advantages over decades-old Wiegand (see our OSDP Access Control Guide) but new IPVM statistics show that usage of OSDP, even...
Verkada Attacks ONVIF on Jun 27, 2019
Verkada has now gone after ONVIF, expanding its attacks against the 'dinosaurs' of the 'ancient' video surveillance industry. In a recent...
FLIR Saros Visible / Thermal Analytic Camera Tested on Jun 26, 2019
FLIR's Saros claims "accurate, actionable alerts" with a combination of 1080p visible and dual thermal sensors along with IR and white light...
IFSEC 2019 Show Report on Jun 19, 2019
The UK's largest trade show, IFSEC, is underway and IPVM has been examining what is new and happening at the show. Inside, we cover: Huawei...
Startup Vaion Launching End-to-End AI Solution Backed with $20 Million Funding on Jun 17, 2019
An EU / USA video surveillance startup, Vaion, founded by ex-Cisco Senior Directors is launching an end-to-end VSaaS platform with $20 million in...
Sighthound Transforms Into Enterprise AI Provider Profile on Jun 14, 2019
Sighthound is now rapidly expanding its R&D team, building an enterprise AI service. This may come as a surprise given their origins 6 years...
OSDP Access Control Guide on Jun 04, 2019
Access control readers and controllers need to communicate. While Wiegand has been the de facto standard for decades, OSDP aims to solve major...
IndigoVision Control Center VMS Tested on May 30, 2019
IPVM's last test of IndigoVision's VMS was in 2010, which found enterprise VMS features and a simple client interface. but no 3rd party camera...
Verkada Favorability Results 2019 on May 29, 2019
Verkada has taken the industry by storm with the fastest growing video surveillance sales organization ever and a half billion dollar valuation....

Most Recent Industry Reports

History of Video Surveillance on Jul 19, 2019
The video surveillance market has changed significantly since 2000, going from VCRs to emerging into an AI cloud era.  The goal of this history...
Mobile Access Usage Statistics 2019 on Jul 18, 2019
The ability to use mobile phones as access credentials is one of the biggest trends in a market that historically has been slow in adopting new...
New GDPR Guidelines for Video Surveillance Examined on Jul 18, 2019
The highest-level EU data protection authority has issued a new series of provisional video surveillance guidelines. While GDPR has been in...
Wyze AI Analytics Tested - Beats Axis and Hikvision on Jul 17, 2019
$20 camera disruptor Wyze has released free person detection deep learning analytics to all of their users, claiming users will "Only get notified...
Anyvision Aims For 2022 Revenue of $1 Billion on Jul 17, 2019
Only 3 video surveillance manufacturers do a billion dollars or more in annual revenue - Hikvision, Dahua, and Axis. Now, Anyvision plans to join...
HD Analog vs IP Guide on Jul 16, 2019
For years, HD resolution and single cable signal/power were IP camera advantages, with analog cameras limited to much lower resolution and...
How To Troubleshoot Wiegand Reader Problems - Inverted Wiring on Jul 16, 2019
Wiegand is the dominant method of connecting access readers, but problems can arise for installers. In fact, one of the most difficult reader...
ZeroEyes Gun Detection Startup on Jul 16, 2019
A gun detection video analytics startup, ZeroEyes, is being led by a group of 6 former Navy SEALs, aiming to "save lives" by using AI to assist...
Motorola Acquires Watchguard, Adds to Vigilant And Avigilon on Jul 15, 2019
2 years ago, Motorola had no position nor relevancy to video surveillance. Now, they own major video surveillance, LPR and body camera providers...
Hikvision Global News Reports Directory on Jul 15, 2019
Hikvision has received the most global news reporting of any video surveillance company, ever, ranging from the WSJ, the Financial Times, Reuters,...

The world's leading video surveillance information source, IPVM provides the best reporting, testing and training for 10,000+ members globally. Dedicated to independent and objective information, we uniquely refuse any and all advertisements, sponsorship and consulting from manufacturers.

About | FAQ | Contact