A dispute broke out on Tuesday after cybersecurity company Rapid7 released a report about a vulnerability in a Fortinet product before the company had time to release a patch addressing the issue.
Rapid7 said one of its researchers, William Vu, discovered an OS command injection vulnerability in version 6.3.11 and prior of FortiWeb’s management interface. The vulnerability allows remote, authenticated attackers to execute arbitrary commands on the system through the SAML server configuration page.
Rapid7 said the vulnerability was related to CVE-2021-22123, which was addressed in FG-IR-20-120. The company added that in the absence of a patch, users should “disable the FortiWeb device’s management interface from untrusted networks, which would include the internet.”
The report included a timeline that said Rapid7 contacted Fortinet about the vulnerability in June and it was acknowledged by Fortinet by June 11. Rapid7 claims they never heard from Fortinet again until they publicly released the report on Tuesday.
A Fortinet spokesperson contacted ZDNet after the story on this vulnerability was published to criticize Rapid7 for violating the terms of their disclosure agreement. Fortinet said it has a clear disclosure policy on its PSIRT Policy page which includes “asking incident submitters to maintain strict confidentiality until complete resolutions are available for customers.”
“We had expected that Rapid7 hold any findings prior to the end of the our 90-day Responsible disclosure window. We regret that in this instance, individual research was fully disclosed without adequate notification prior to the 90-day window,” the Fortinet spokesperson said, adding that they often work closely with researchers and vendors on cybersecurity.
“We are working to deliver immediate notification of a workaround to customers and a patch released by the end of the week.”
Fortinet did not respond to follow up questions about the patch for the vulnerability.
Rapid7 updated their report to say that Fortiweb 6.4.1 will be released at the end of August and will have a fix for the vulnerability.
Tod Beardsley, director of research at Rapid7, told ZDNet that their vulnerability disclosure policy outlines a 60-day minimum for disclosing vulnerabilities after initial contact attempts.
“In this instance, the initial disclosure was presented to Fortinet on June 10 and a vendor ticket was received on June 11, per our disclosure report. We made several follow-up attempts with Fortinet following that initial communication and unfortunately we received no response back after 66 days,” Beardsley explained.
“There was no violation of disclosure policies. Shortly after publishing the disclosure, we were in contact with Fortinet and they indicated they will be releasing a fix. Once that fix is released, we’ll update our disclosure with that link and CVE ID.”
Beardsley added that there is no indication the vulnerability has been used, so Rapid7’s disclosure “should be read as a cautionary piece for users of Fortinet’s FortiWeb.”
He reiterated that users of FortiWeb should not expose their management interface to the internet in general and should make sure that the people with authentication credentials are picking solid, strong passwords.
- Kaseya ransomware attack: What you need to know
- Surfshark VPN review: It’s cheap, but is it good?
- The best browsers for privacy
- Cyber security 101: Protect your privacy
- The best antivirus software and apps
- The best VPNs for business and home use
- The best security keys for 2FA
- How victims who pay the ransom encourage more attacks (ZDNet YouTube)