Fortinet white logo
Fortinet white logo

Resolved issues

Resolved issues

The following issues have been resolved in FortiADC 7.4.5 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID

Description

1069133 False positives for SQL/XSS Injection Detection are triggered by legitimate requests containing Arabic language characters.
1067899 Unable to edit real servers from the FortiView Local Topology.
1066100 Unable to assign a /31 subnet IP to the interface for a point-to-point connection.
1054660 When configuring a REST API Administrator, the API key cannot be generated if the setup is done through the Global configuration without access to the root VDOM.
1042724 A core dump was triggered due to a socket in the process of closing during the socket dump operation, causing the issue to occur.
1042085 Unable to delete a script — the error message states that the script is applied to a Layer 4 virtual server, which does not support scripting.
1039565 The Authentication Policy with Server Load Balancing is truncating "-" from usernames.
1036480 FortiADC unable to synchronize HA cluster due to WAF signature database upgrade.
1034384 Unable to log in to FortiADC appliance through GUI when /tmp folder reaches 90% capacity.
1034357 LDAPS negotiation failure with TLS 1.0 post upgrade from 7.4.0 to 7.4.3.
1031727 Httproxy crash related to OpenSSL issue — resolved by upgrading to OpenSSL version 3.1.5.
1030563 High latency issue caused by httproxy utilizing 100% CPU when the Exception List is enabled and the client unsuccessfully initiates the TLS handshake.
1015996 Newly imported certificate/private key is not being accepted.
1009204 Some virtual servers are not responding, with traffic logs showing 0 bytes sent or received.
1001089 VIP is not accessible on 400F port9 and port10 when packet capture is disabled.
Common Vulnerabilities and Exposures

For more information, visit https://www.fortiguard.com/psirt.

Bug ID

Description

1051921 FortiADC 7.4.5 is no longer vulnerable to the following CVE-Reference: CVE-2024-6387.

Resolved issues

Resolved issues

The following issues have been resolved in FortiADC 7.4.5 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID

Description

1069133 False positives for SQL/XSS Injection Detection are triggered by legitimate requests containing Arabic language characters.
1067899 Unable to edit real servers from the FortiView Local Topology.
1066100 Unable to assign a /31 subnet IP to the interface for a point-to-point connection.
1054660 When configuring a REST API Administrator, the API key cannot be generated if the setup is done through the Global configuration without access to the root VDOM.
1042724 A core dump was triggered due to a socket in the process of closing during the socket dump operation, causing the issue to occur.
1042085 Unable to delete a script — the error message states that the script is applied to a Layer 4 virtual server, which does not support scripting.
1039565 The Authentication Policy with Server Load Balancing is truncating "-" from usernames.
1036480 FortiADC unable to synchronize HA cluster due to WAF signature database upgrade.
1034384 Unable to log in to FortiADC appliance through GUI when /tmp folder reaches 90% capacity.
1034357 LDAPS negotiation failure with TLS 1.0 post upgrade from 7.4.0 to 7.4.3.
1031727 Httproxy crash related to OpenSSL issue — resolved by upgrading to OpenSSL version 3.1.5.
1030563 High latency issue caused by httproxy utilizing 100% CPU when the Exception List is enabled and the client unsuccessfully initiates the TLS handshake.
1015996 Newly imported certificate/private key is not being accepted.
1009204 Some virtual servers are not responding, with traffic logs showing 0 bytes sent or received.
1001089 VIP is not accessible on 400F port9 and port10 when packet capture is disabled.
Common Vulnerabilities and Exposures

For more information, visit https://www.fortiguard.com/psirt.

Bug ID

Description

1051921 FortiADC 7.4.5 is no longer vulnerable to the following CVE-Reference: CVE-2024-6387.