At the recent Black Hat 2019 conference held in Las Vegas this past August 3-8, security researchers discussed their discovery of security vulnerabilities that impacted several security vendors, including Fortinet. All of the vulnerabilities impacting Fortinet were fixed in April and May of 2019.
Two of the vulnerabilities directly affected Fortinet’s implementation of SSL VPN. They are:
In addition, it was also disclosed (and fixed) in May 2019 that FortiOS included a “magic” string value that had been previously created at the request of a customer to enable users to implement a password change process when said password was expiring. That function had been inadvertently bundled into the general FortiOS release, and an Improper Authorization vulnerability resulted in that value being usable on its own to remotely change the password of an SSL VPN web portal user without credentials.
NOTE: only users with local authentication were affected - SSL VPN users with remote authentication (LDAP or RADIUS) were not impacted. Here are the details:
In May, FortiGuard Labs released patches for CVE-2018-13379, CVE-2018-13383, and CVE-2018-13382. The errant code string has also been removed from the FortiOS code base. A patch has also been released for all affected versions of FortiOS for this vulnerability. FortiGuard signatures have also been deployed to monitor attack traffic in the wild and enable a FortiGuard response. FortiGuard Labs continues to actively monitor attack activity worldwide and will provide additional updates when necessary.
Customer security is our first priority and we continue to proactively communicate with our customers. We urge customers to immediately implement all appropriate patch updates and signatures, with a firmware upgrade still the primary recommended solution.
In addition to industry-leading best practices, we follow and comply with regular review processes that include multiple tiers of inspection, internal and third-party audits, and automated triggers and tools across the entire development of our source code.
We have strengthened our processes and best practices, including:
• Yearly secure code training
• RTF (remediate the flag) tournaments for developers
• A bug identification incentive program
• Mandatory sign off on our Secure Coding Handbook for developers based on OWASP and industry best practices
• Periodic black box assessments of products using an adversary approach and performed by different independent third parties
• Automated monitoring of the vulnerability landscape via web and mailing lists crawlers