Fortinet white logo
Fortinet white logo

Resolved issues

Resolved issues

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

Bug ID

Description

1073584

dnsd needs to synchronize the FQDN real server IP from the Config Primary.

1103175

Stronger recommendations to upgrade RAM are needed when the system detects insufficient memory for standard operation.

1101643 Unable to change password in cloudinit due to AWS user data issue.
1096464 FortiADC's SSH server public key length is insufficient. The recommended minimum RSA public key length is 2048 bits or greater.
1095322 SNMPv3 response issue.
1083458 The miglogd process crashes when the FortiAnalyzer server IP address is configured as 0.0.0.0.
1083424 The SSL handshake error "unsafe legacy renegotiation disabled" occurs if the real server does not support the renegotiation extension.
1079989 Traffic logs cannot be displayed on the GUI due to improper deletion of outdated log data when the log file exceeds the 1.5 GB size limit.
1077477 When changing the primary network interface IP on the Azure platform, the MAC address of the associated port on FortiADC changes. This results in the new IP address becoming unreachable.
1074906 FortiADC crashes when the tcp_slow_data_attack is triggered.
1073974 Invalid DNS server responses, specifically 3 (NXDOMAIN) indicating "Non-Existent Domain" and 5 (REFUSED) indicating "Query Refused," are intercepted and suppressed, preventing these response codes from being forwarded back to the client.
1071363 The fcnacd process crashes due to the EMS configuration being absent.
1056086 Passive cookie persistence cannot be configured for content routing through the GUI.
1029802 Connection to EMS fails because the server certificate or the configured certificate is not recognized.
Common Vulnerabilities and Exposures

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

Bug ID

Description

1055674 FortiADC 7.4.6 is no longer vulnerable to the following CVE-Reference: CVE-2024-3596.

Resolved issues

Resolved issues

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

Bug ID

Description

1073584

dnsd needs to synchronize the FQDN real server IP from the Config Primary.

1103175

Stronger recommendations to upgrade RAM are needed when the system detects insufficient memory for standard operation.

1101643 Unable to change password in cloudinit due to AWS user data issue.
1096464 FortiADC's SSH server public key length is insufficient. The recommended minimum RSA public key length is 2048 bits or greater.
1095322 SNMPv3 response issue.
1083458 The miglogd process crashes when the FortiAnalyzer server IP address is configured as 0.0.0.0.
1083424 The SSL handshake error "unsafe legacy renegotiation disabled" occurs if the real server does not support the renegotiation extension.
1079989 Traffic logs cannot be displayed on the GUI due to improper deletion of outdated log data when the log file exceeds the 1.5 GB size limit.
1077477 When changing the primary network interface IP on the Azure platform, the MAC address of the associated port on FortiADC changes. This results in the new IP address becoming unreachable.
1074906 FortiADC crashes when the tcp_slow_data_attack is triggered.
1073974 Invalid DNS server responses, specifically 3 (NXDOMAIN) indicating "Non-Existent Domain" and 5 (REFUSED) indicating "Query Refused," are intercepted and suppressed, preventing these response codes from being forwarded back to the client.
1071363 The fcnacd process crashes due to the EMS configuration being absent.
1056086 Passive cookie persistence cannot be configured for content routing through the GUI.
1029802 Connection to EMS fails because the server certificate or the configured certificate is not recognized.
Common Vulnerabilities and Exposures

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

Bug ID

Description

1055674 FortiADC 7.4.6 is no longer vulnerable to the following CVE-Reference: CVE-2024-3596.