Resolved issues

To inquire about a particular bug, please contact Fortinet Customer Service & Support.

• For some FortiCam FD51, FD55-CA, and FE120B cameras, network settings were not retained after a factory reset

• For a FortiCam FE120B in fisheye display mode with shutter WDR enabled, an extra-high resolution screenshot could not be retrieved

• For FortiCam FD51, the digital input trigger default value should be set to Low

• If a FortiCam FD55-CA was on a different subnet than FortiRecorder, its MAC address was not correctly detected

• If a FortiCam MC51 view was rotated ±90°, the camera could crash

• Motion detection search analytics did not have results

• After a factory reset on FortiCam FE120B or FD55-CA, analytics configuration could fail

• When VLC was used to seek backwards on a video stream, the video stream service stopped

• Camera simulator should function on FortiRecorder-VM platforms

• If more than 4 cameras were added to FortiRecorder 100G, it became unresponsive

• If more than 16 cameras were added to FortiRecorder 400F, it became unresponsive

• Bug ID 1059479: If more than 4 cameras were added to Service > Monitor Display on FortiRecorder 100G, it became unresponsive

• Bug ID 1081765: Camera motion detection event recordings did not work if the

• Bug ID 1074820: If SFTP remote configuration backup fails, FortiRecorder should generate a log message

• Bug ID 1053197: After upgrading a FortiRecorder, the ONVIF transport type and port should not be reset to their default values

Vulnerabilities

• Bug ID 1092957, 1082353: CLI path traversal attack

• Bug ID 1082354: GUI path traversal attack

• Bug ID 1092984: Upgrade to httpd 2.4.62

• Bug ID 1057588: Security fabric (csfd) daemon inserted sensitive information into data that it sends

• Bug ID 1060912: Security fabric (csfd) daemon path traversal attack