Resolved Issues
The following issues have been fixed in FortiSandbox 5.2.0. For inquiries about a particular bug, contact Customer Service & Support.
GUI
|
Bug ID |
Description |
|---|---|
|
0627506 |
Fixed an issue where the authentication method was not displayed after creating a user with two‑factor authentication enabled. |
|
1144262 |
Fixed an issue where on‑demand direct URL submissions did not support port numbers. |
|
1210323 |
Fixed an issue with improper session handling. |
|
1215283 |
Fixed an issue where CSRF verification failed when creating a local or LDAP administrator account. |
|
1234396 |
Fixed an issue where FortiSandbox in air‑gap mode showed the FortiGuard update status as Unknown after a reboot. |
|
1239465 |
Fixed an issue where FQDNs containing dashes could not be added as NTP servers. |
|
1289866 |
Fixed a FortiGuard update issue by adding support for both current and upcoming FDN server certificates. |
Fabric integration and Deployment
|
Bug ID |
Description |
|---|---|
| 1180040 | Fixed an issue where FortiSandbox attempted to resolve mac, mac2, fsavm, and fqdl when deployed in air‑gap mode. |
|
1236888 |
Fixed an issue where FortiGuard AV updates caused timeouts for the ICAP client. |
|
1281865 |
Fixed an issue where PNG, JPG, or TXT files were not submitted to FortiSandbox from FortiGate when the FSA primary was in management mode. |
|
1283995 |
Fixed an issue where srcip/dev fields from ICAP traffic were sometimes incorrect in a cluster environment. |
|
1284615 |
Fixed an issue where users could not save the configuration when the Share Path included a “$” character. |
Scan and Engine
|
Bug ID |
Description |
|---|---|
| 1191884 | Dynamic scan performance on FSA KVM VMs running FC4 with 128 CPUs is lower than on FC3 with 64 CPUs. |
|
1201522 |
Fixed issue of malware package if upgraded to 5.0.4 from prior 5.0.2. |
|
1218631 |
Fixed an issue where the system was still querying the APT server when the remote Windows cloud VM was disabled. |
|
1221200 |
Fixed an issue where the Sandbox quarantine placeholder file did not replace the original file. |
|
1223830 |
Fixed an issue where malicious files were not detected when FortiSandbox Community Cloud was disabled. |
|
1223830 |
Fixed an issue where malicious files were not detected when FortiSandbox Community Cloud was disabled. |
|
1247162 |
Fixed invalid utf8 due to truncated string. |
|
1251514 |
Fixed the Job Archive feature failed to archive files. |
|
1253309 |
Fixed an issue where an EXE file renamed as a ZIP was not correctly identified. |
System & Security
|
Bug ID |
Description |
|---|---|
|
1196029 |
Resolved an issue where FSA-1000F units lost embedded Windows/Office licenses after upgrading to version 5.0.4. |
|
1228856 |
Hardened TLS configuration by removing insecure cipher suites from management interfaces to address vulnerability scan findings. |
|
1258885 |
Enhanced cluster communication port tolerance to avoid failover caused by short network jitter. |
Logging & Reporting
|
Bug ID |
Description |
|---|---|
|
1171394 |
Fixed an issue with corrupted archive file logging and customized ratings. |
| 1260137 | Fixed an SNMPv3 polling failure on FortiSandbox 500F. |
CLI and API
|
Bug ID |
Description |
|---|---|
|
1196097 |
Fixed an issue where script‑type executable files did not require the correct file extension; this option is now enabled by default. |
|
1226626 |
Fixed the show command displaying member ports even after they were assigned to a bonded interface. |
|
1230769 |
Fixed an issue where read-only LDAP accounts created through the CLI were unable to authenticate. |
Common vulnerabilities and exposures
|
Bug ID |
Description |
|---|---|
|
1245752 |
FortiSandbox 5.2.0 is no longer vulnerable to the following CVE Reference:
|