Resolved issues
The following issues have been fixed in FortiProxy 7.2.15. For inquiries about a particular bug, please contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 1164161 | The first LDAP cache query always fails, even when both user node and group info are correct. |
| 1163276 | reportd crash after deployment on AliCloud. |
| 1164508, 1183151 | Issue with machine account authentication in NTLM and Kerberos. |
| 1178564 | Unable to access any websites intermittently in explicit proxy. |
| 1154043 | Fix incorrect locking and RCU usage in kernel. |
| 1177934 | WAD workers are at 99% CPU for more than 10 minutes after a firewall policy is enabled or disabled, impacting traffic. |
| 1177573 | Issues related to error handling with wad_str objects and buffer operations. |
| 1161593 | Cannot configure ssl-ssh-profile for explicit-web policy with action redirect. |
| 1170884 | FortiProxy repeatedly reboots. |
| 1104165 | GUI and CLI output for firewall and proxy authentication lists mismatch. |
| 1161799 | Incorrect MTU used for IPsec tunnel. |
| 1200594 | After uploading image to a HA cluster, the active unit responds passive unit's MAC address to the ARP request, which leads to client wrongly connect to the passive unit when trying to access the cluster with the cluster IP. |
| 1177720 | Cannot connect to FortiGate Cloud. |
| 776013, 1180097 | Authentication refactor to support multiple authentication request so as to prevent race condition. |
| 1173584 | Bypass for oversize files does not work. |
Common vulnerabilities and exposures
FortiProxy 7.2.15 is no longer vulnerable to the following CVE reference. Visit https://fortiguard.com/psirt for more information.
|
Bug ID |
CVE reference |
|---|---|
|
1187887, 1192040 |