November 15, 2019
Fortinet FortiClient for Linux is prone to multiple local security vulnerabilities. An attacker may exploit these issues to inject and execute arbitrary system-commands with root privileges, overwrite system-files, gain elevated privileges or cause denial of service conditions. Versions prior to FortiClient for Linux 6.2.2 are vulnerable.
- Fortinet FortiClient 5.4.0
- Fortinet FortiClient 5.4.1
- Fortinet FortiClient 5.4.2
- Fortinet FortiClient 5.4.3
- Fortinet FortiClient 5.4.4
- Fortinet FortiClient 5.6
- Fortinet FortiClient 5.6.0
- Fortinet FortiClient 5.6.1
- Fortinet FortiClient 6.0.1
- Fortinet FortiClient 6.0.2
- Fortinet FortiClient 6.0.3
- Fortinet FortiClient 6.0.4
- Fortinet FortiClient 6.0.5
- Fortinet FortiClient 6.0.6
- Fortinet FortiClient 6.0.7
- Fortinet FortiClient 6.0.8
- Fortinet FortiClient 6.2.0
- Fortinet FortiClient 6.2.1
Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
Restrict local access to trusted and accountable individuals only.
Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.
Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as non-executable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploits of memory-corruption vulnerabilities.
Updates are available. Please see the references or vendor advisory for more information.
Cees Elzinga from Langkjaer Cyber Defence.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.