inSync Client v7.0.1 for Cloud
An update for inSync Client is released on September 22, 2021, with the following fixed issue.
|INS-25732||Fixed URL injection vulnerability by adding validation so that no arbitrary URL can be added to load a malicious page.|
inSync Client v7.0.0 update on July 24, 2021
The following enhancement is available with this release dated July 24, 2021:
Enhancements to data restore
You can now restore the data to the original location across devices when you have more than one device configured. You can restore the data to the original location across the devices of the same OS platform.
For more information, see Restore data using inSync Client.
Druva has not released a new version of inSync Client for Linux OS with inSync Client v7.0.0. You can continue using inSync Client v5.9 for Linux with inSync Cloud.
Download the latest inSync Client here.
For upgrade instructions, see Upgrade the inSync Client.
To learn more, contact Support.
|INS-14039||inSync Client: Fixed an issue for the MAPI restore where the MAPI restores failed frequently.|
|INS-25497||inSync Client: A command execution vulnerability in the local http server, wherein an un-trusted filename parameter is received and is passed without any validation has been fixed.|
|INS-25496||inSync Client: A code injection vulnerability via DYLD library linking was identified in the macOS client and has been fixed by altering app entitlements and restricting dynamic library loading via environment variables.|
|INS-25493||inSync Client: Fixed a security vulnerability for de-serialization by changing the signature format to the non-binary protocol which will now restrict suspicious upgrade package signature.|
|INS-18820||inSync Client: Fixed an issue in the inSync Client log and inSync Client UI where it showed a masked error and not the actual error|
|INS-20142||inSync Client: Fixed an issue in the client log wherein the log does not specify the correct restore status in case of device refresh.|
|INS-22600||inSync Client: Fixed an issue for the SSO, wherein login failed, when the proxy setup is enabled for the user.|
|INS-24905||inSync Client: Fixed an issue for the activation failure, wherein the activation failed on devices with a large number of certificates.|