Resolved issues
The following issues have been resolved in the FortiDDoS-F 6.3.2 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
Bug ID |
Description |
---|---|
0805074/0787761 |
If any condition causes the system Virtual Packet Processing engine to restart, Traffic Statistics become unusable and may affect traffic and/or Thresholds. The root cause of this issue also resulted in the following issue: In Asymmetric Mode with Asymmetric Mode Allow Inbound Synack, in Prevention Mode, the SYN-ACK traffic stats were not reset correctly after each measurement cycle and eventually crossed the SYN-ACK In Asymmetric Mode Threshold was crossed causing SYN-ACK drops affecting legitimate traffic. |
0804753 | If SPP Layer 3 Thresholds are set to factory default via CLI, the Most Active Destination Threshold was not reset. Most Active Destination Threshold is not set by System Recommendations and is only set manually when required. |
0797576 | Under QA testing, it was possible to crash the Virtual Packet Processing engine with HTTP Floods. |
0795940 | Under stress testing some extraneous messages were seen in the Console output. |
0769847 | Importing a security certificate might return "The imported local certificate is invalid" error. |
Common Vulnerabilities and Exposures
For more information, visit https://www.fortiguard.com/psirt.
Bug ID |
Description |
---|---|
0790805 |
FortiDDoS-F 6.3.2 is no longer vulnerable to the following CVE/CWE-References: CWE-78: Improper Neutralization of Special Elements used in an OS Command ("OS Command Injection"). |