{"vuid":"VU#822980","idnumber":"822980","name":"SysLINK M2M Modular Gateway contains multiple vulnerabilities","keywords":["hard-coded","command injection","crypto","password"],"overview":"The SysLINK SL-1000 M2M (Machine-to-Machine) Modular Gateway contains multiple vulnerabilities.","clean_desc":"According to the researcher, the SysLINK SL-1000 M2M Modular Gateway contains multiple vulnerabilities: CWE-259: Use of Hard-coded Password - CVE-2016-2331 By default, the device's web interface uses a default password across all devices and does not prompt the administrator to change that password. CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') - CVE-2016-2332 The device's web interface runs as the root user and is vulnerable to command injection via an authenticated POST request to flu.cgi. The parameter \"5066\" (dnsmasq) is vulnerable to injection. Commands are constructed and run as the root user. CWE-321: Use of Hard-coded Cryptographic Key - CVE-2016-2333 The device uses an encryption key that is hard-coded and believed to be static across the entire device population. The CERT/CC has been unable to confirm these vulnerabilities with the vendor. It is also unclear if models other than the SL-1000 are affected.","impact":"An unauthenticated remote attacker with knowledge of the password may obtain root access to the device.","resolution":"Apply an update According to the reporter, affected users should update to firmware version 01A.8 which addresses these issues. CERT/CC has reached out to Systech to confirm this information. Additionally, affected users may consider the following workarounds and mitigations:","workarounds":"Restrict Network Access As a general good security practice, only allow connections from trusted hosts and networks. Consult your firewall product's manual for more information.","sysaffected":"","thanks":"Thanks to Roman Faynberg and Jeremy Allen of Carve Systems for reporting this vulnerability.","author":"This document was written by Garret Wassermann.","public":[],"cveids":["CVE-2016-2331","CVE-2016-2332","CVE-2016-2333"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2015-05-06T17:50:16Z","publicdate":"2016-04-22T00:00:00Z","datefirstpublished":"2016-04-22T17:30:23Z","dateupdated":"2016-04-22T17:37:41Z","revision":29,"vrda_d1_directreport":"1","vrda_d1_population":"3","vrda_d1_impact":"3","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":"C","cvss_collateraldamagepotential":"ND","cvss_targetdistribution":"M","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":"9.5","cvss_environmentalscore":"7.121077488","cvss_environmentalvector":"CDP:ND/TD:M/CR:ND/IR:ND/AR:ND","metric":0.0,"vulnote":null}