{"vuid":"VU#301735","idnumber":"301735","name":"Zmodo ZP-NE14-S DVR and ZP-IBH-13W cameras contain hard-coded credentials","keywords":["hard-coded","CWE-798","telnet"],"overview":"The Zmodo ZP-NE14-S DVR and ZP-IBH-13W cameras contain hard-coded credentials and run telnet by default.","clean_desc":"CWE-798: Use of Hard-coded Credentials - CVE-2016-5081 According to the reporter, the Zmodo ZP-NE14-S DVR and ZP-IBH-13W cameras contain undocumented credentials for accessing the device via telnet. These credentials allow root access to the device, and are hard-coded and cannot be changed by the user. Additionally, these cameras contain an always running instance of telnet that allows network access by an attacker. Telnet cannot be disabled. CWE-636: Not Failing Securely ('Failing Open') - CVE-2016-5650 According to the reporter, the Zmodo ZP-NE14-S DVR and ZP-IBH-13W cameras can be forced to deauthenticate and connect to an unencrypted network with the same SSID, even if the device settings specify use of encryption such as WPA2, as long as the competing network has a stronger signal. An attacker must be able to set up a nearby SSID, similar to an \"Evil Twin\" attack. The CERT/CC has to-date been unable to reach the vendor to confirm these vulnerabilities.","impact":"A remote unauthenticated attack with knowledge of the credentials may gain root access to the device.","resolution":"Apply an update The CERT/CC has received the following statement from Zmodo: Zmodo has released firmware Version 40.0.3.0 (for ZP­NE14­S) and firmware Version 7.8.0.36 (for ​ZP­IBH­13W) to address these issues. Affected users are encouraged to use their mobile phone with Zmodo APP installed to upgrade their \nZmodo devices to the latest firmware as soon as possible. Please see their support announcement here.","workarounds":"","sysaffected":"","thanks":"Thanks to \nGarrett Miller and John Kotheimer\n for reporting this vulnerability.","author":"This document was written by Garret Wassermann.","public":["http://files.zmodo.com/others/vu301735.pdf","http://cwe.mitre.org/data/definitions/798.html"],"cveids":["CVE-2016-5081","CVE-2016-5650"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2016-05-04T19:48:37Z","publicdate":"2016-08-11T00:00:00Z","datefirstpublished":"2016-08-12T14:56:14Z","dateupdated":"2016-08-26T14:47:31Z","revision":20,"vrda_d1_directreport":"1","vrda_d1_population":"1","vrda_d1_impact":"1","cam_widelyknown":"0","cam_exploitation":"0","cam_internetinfrastructure":"0","cam_population":"0","cam_impact":"0","cam_easeofexploitation":"0","cam_attackeraccessrequired":"0","cam_scorecurrent":"0","cam_scorecurrentwidelyknown":"0","cam_scorecurrentwidelyknownexploited":"0","ipprotocol":"","cvss_accessvector":"N","cvss_accesscomplexity":"L","cvss_authentication":null,"cvss_confidentialityimpact":"C","cvss_integrityimpact":"C","cvss_availabilityimpact":"C","cvss_exploitablity":null,"cvss_remediationlevel":"U","cvss_reportconfidence":"UR","cvss_collateraldamagepotential":"ND","cvss_targetdistribution":"L","cvss_securityrequirementscr":"ND","cvss_securityrequirementsir":"ND","cvss_securityrequirementsar":"ND","cvss_basescore":"10","cvss_basevector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","cvss_temporalscore":"8.5","cvss_environmentalscore":"2.1363232464","cvss_environmentalvector":"CDP:ND/TD:L/CR:ND/IR:ND/AR:ND","metric":0.0,"vulnote":null}