Resolved Issues
The following issues have been fixed in FortiSandbox 4.2.0. For inquiries about a particular bug, contact Customer Service & Support.
Bug ID |
Description |
---|---|
755708 | Fixed admin profile read-write issue on the dashboard widget to perform firmware upgrade. |
Fabric integration
Bug ID |
Description |
---|---|
774786 | Fixed encoding issue of unicode characters on API query of job detail. |
770796 |
Fixed content-type changed issue on NetShare scan of AWS deployment. |
764185 |
Fixed broken web page issue on ICAP deployment due to no encoding support. |
790423 | FortiSandbox fails to download packages from FortiManager. For details, see Special Notices. |
HA Cluster
Bug ID |
Description |
---|---|
694610 | Issues about cluster external/internal interface |
Scan
Bug ID |
Description |
---|---|
780955 | Fixed download tracer log for failed scan. |
760045 | Fixed override server issue on web filtering query. |
774122 |
Fixed timeout issue on custom RHEL8 VM due to lack of memory resource. |
System & Security
Bug ID |
Description |
---|---|
783344 |
Fixed conserve mode state issue due to undefined limit on sniffer mode deployment specific to 3000F model. |
694610 |
Fixed configuration issue that allows using similar interface for both external and internal networking. |
783889 |
Fixed gratuitous ARP issue on HA-cluster fail-back scenario. |
792003 |
Fixed configuration synchronization issue of SNMP to secondary unit. |
668581 |
Upgraded JQuery library to latest stable version. |
742300 |
Fixed booting hung issue after executing factory-reset. |
783889 |
Fixed gratuitous ARP issue on HA-cluster fail-back scenario. |
Logging & Reporting
Bug ID |
Description |
---|---|
764486 |
Fixed wrong timezone issue on syslog (e.g. FortiSIEM). |
707073 |
Fixed missing system event log for downloading job details such as Tracer Package. |
Common vulnerabilities and exposures
Bug ID |
Description |
---|---|
683306 |
FortiSandbox4.2.0 is no longer vulnerable to the following CVE Reference:
|
719039 |
FortiSandbox4.2.0 is no longer vulnerable to the following CVE Reference:
|