{"vuid":"VU#428280","idnumber":"428280","name":"CSL DualCom GPRS CS2300-R alarm signalling boards contain multiple vulnerabilties","keywords":["crypto","authentication","csl dualcom","cs2300-r","secure premises transmitter","hardcoded pin","undocumented commands"],"overview":"CSL DualCom GPRS CS2300-R alarm signalling boards, firmware versions v1.25 to v3.53, contain multiple vulnerabilties.","clean_desc":"CSL DualCom GPRS CS2300-R alarm signalling boards are secure premises transmitters (SPT) that notify alarm receiving centers (ARC) when an alarm system is tripped. According to researcher Andrew Tierney, CS2300-R boards are vulnerable to signal spoofing and tampering due to the vendor's use of a weak communications protocol and proprietary encryption scheme. The vendor has generally disputed the researcher's findings with the following statement: - As with all our products, this product has been certified as compliant to the required European standard EN-50136\n- Our internal review of the report concluded there is no threat to these systems For the full vendor statement, refer to the Vendor Information section below. For full details about the vulnerabilities and their discovery, refer to the researcher's disclosure. CWE-287: Improper Authentication - CVE-2015-7285 Communications between CS2300-R SPTs and ARC polling servers are not mutually authenticated. Consequently, the SPT cannot confirm the authenticity of messages received from ARC servers. An attacker capable of performing man in the middle (MITM) attacks can spoof responses that will be accepted as valid by vulnerable SPTs. CWE-327: Use of a Broken or Risky Cryptographic Algorithm - CVE-2015-7286 Communications between CS2300-R SPTs and ARC servers are encrypted using a proprietary encryption scheme. A number of issues are identified by the researcher by which messages can be decrypted or otherwise manipulated, resulting in denial of service, false alarms, suppressed alarms, and a general inability to trust communications bilaterally. Combined with the previously described lack of mutual authentication, a capable attacker may be able to bilaterally spoof or block any messages between endpoints. Specifically, the following issues are described by the researcher: the encryption algorithm is a polyalphabetic substitution cipher and subject to decryption via common cryptanalytic techniques\nencryption keys (mapping tables for substitution) are hardcoded in the firmware and have not changed from v1.25 to v3.53\neffective key length is very short\nmessages do not contain sequence numbers\nmessages do not make use of checksums or hashes\nmessages do not contain message authentication codes (MAC)\nkey material cannot be readily updated\nsensitive SPT identification information can be obtained by capturing and analyzing single messages CWE-255: Credentials Management - CVE-2015-7287 CS2300-R SPTs make use of a non-unique, default PIN code to restrict users from issuing remote commands via SMS. An attacker may use the default PIN to issue remote commands to vulnerable devices. CWE-912: Hidden Functionality - CVE-2015-7288 CS2300-R SPTs contain multiple undocumented SMS commands that can be used to alter the configuration of devices. The CVSS score reflects CVE-2015-7286.","impact":"A remote, unauthenticated attacker may be able to decrypt communications and spoof messages between SPTs and ARCs, resulting in denial of service, false alarms, suppressed alarms, and a general inability to trust communications bilaterally.","resolution":"The CERT/CC is currently unaware of a practical solution to this problem. According to the researcher, hardware limitations may render a cryptographic solution difficult while maintaining current functionality. Note that the vendor has generally disputed the researcher's findings with the following statement: - As with all our products, this product has been certified as compliant to the required European standard EN-50136\n- Our internal review of the report concluded there is no threat to these systems","workarounds":"","sysaffected":"","thanks":"Thanks to Andrew Tierney for reporting these vulnerabilities.","author":"This document was written by Joel Land.","public":["http://www.csldual.com/uk/","http://cybergibbons.com/?p=2844","https://cwe.mitre.org/data/definitions/287.html","https://cwe.mitre.org/data/definitions/327.html","https://cwe.mitre.org/data/definitions/255.html","https://cwe.mitre.org/data/definitions/912.html"],"cveids":["CVE-2015-7285","CVE-2015-7286","CVE-2015-7287","CVE-2015-7288"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2015-10-02T16:47:22Z","publicdate":"2015-11-23T00:00:00Z","datefirstpublished":"2015-11-23T14:19:10Z","dateupdated":"2015-11-23T14:30:24Z","revision":29,"vrda_d1_directreport":"1","vrda_d1_population":"2","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":"M","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":"9.3","cvss_basevector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","cvss_temporalscore":"8","cvss_environmentalscore":"1.9947516624","cvss_environmentalvector":"CDP:ND/TD:L/CR:ND/IR:ND/AR:ND","metric":0.0,"vulnote":null}