{"vuid":"VU#319904","idnumber":"319904","name":"Pulse Secure Linux client GUI fails to validate SSL certificates","keywords":["Tapioca"],"overview":"The Pulse Secure Linux client GUI fails to validate SSL certificates, which can allow an attacker to modify connection settings.","clean_desc":"Pulse Secure is an SSL VPN solution. The Linux Pulse Secure client GUI is implemented using WebKit, and the actions taken using the GUI are implemented by overriding JavaScript functions. The WebKit component of the Linux Pulse Secure client GUI is configured to ignore SSL validation errors. This means that when the Pulse Secure Linux client GUI is used to connect to a VPN server on an untrusted network, an attacker may be able to take actions that occur as the result of a user interacting with the Pulse Secure GUI. For example, an attacker may be able to modify or create new VPN connections in the Pulse Secure GUI. An attacker can also modify the welcome message that the Pulse Secure client GUI displays to the user when a VPN connection is established as well.","impact":"By modifying traffic between a Pulse Secure Linux client GUI and a server, an attacker may be able to take actions in the Pulse Secure client GUI, as well as modify information presented to the user. This may result in the user connecting to a malicious VPN server.","resolution":"Apply an update This issue is addressed in Pulse Secure versions PULSE5.3R4.2 Software (Build 639) and PULSE5.2R9.2 Software (Build 638). Please see Pulse Secure advisory SA43620 - 2018-01 for more details. If you are unable to apply an update, please consider the following workaround:","workarounds":"Use the Pulse Secure Linux client CLI By avoiding the use of the Pulse Secure Linux client GUI, the vulnerable code that does not validate certificates can be avoided. Do not use the Pulse Secure Linux client GUI on untrusted networks By not using the Pulse Secure Linux client GUI on an untrusted network, the risk of exploitation of this vulnerability can be minimized.","sysaffected":"","thanks":"This vulnerability was reported by Will Dormann of the CERT/CC.","author":"This document was written by Will Dormann.","public":["h","t","t","p",":","/","/","k","b",".","p","u","l","s","e","s","e","c","u","r","e",".","n","e","t","/","a","r","t","i","c","l","e","s","/","P","u","l","s","e","_","S","e","c","u","r","i","t","y","_","A","d","v","i","s","o","r","i","e","s","/","S","A","4","3","6","2","0"],"cveids":["CVE-2018-6374"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2017-12-08T23:16:19Z","publicdate":"2018-02-01T00:00:00Z","datefirstpublished":"2018-02-01T22:29:44Z","dateupdated":"2018-02-01T22:29:44Z","revision":7,"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":"H","cvss_authentication":null,"cvss_confidentialityimpact":"P","cvss_integrityimpact":"P","cvss_availabilityimpact":"P","cvss_exploitablity":null,"cvss_remediationlevel":"OF","cvss_reportconfidence":"C","cvss_collateraldamagepotential":"ND","cvss_targetdistribution":"M","cvss_securityrequirementscr":"ND","cvss_securityrequirementsir":"ND","cvss_securityrequirementsar":"ND","cvss_basescore":"5.1","cvss_basevector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","cvss_temporalscore":"4","cvss_environmentalscore":"2.99514857509744","cvss_environmentalvector":"CDP:ND/TD:M/CR:ND/IR:ND/AR:ND","metric":0.0,"vulnote":null}