Fortinet white logo
Fortinet white logo

Resolved Issues

Resolved Issues

The following important issues have been fixed in FortiSOAR release 7.3.2. This release also includes important security fixes. To inquire about a particular bug, please contact Customer Service & Support.

Security Fixes

Bug ID Description

0882107, 0883505

Fixes for possible privilege escalations.

0885301

Fixed issues with renewing the Threat Intelligence Management license.

Other Fixes

Bug ID Description

0880816

Groups (blocks) in playbooks were not getting deleted even when a playbook was permanently deleted, i.e., removed from the recycle bin.

0882106

Uniqueness constraint validation was being honored while importing modules in Solution Packs that could cause the import to fail. Now, the uniqueness constraint validation in the case of modules in Solution Packs is skipped. For example, if an existing 'Alert' module has uniqueness constraint defined on 'Source' and 'SourceID' fields and you import a solution pack with uniqueness constraint defined on 'SourceID' and 'Name' fields for the 'Alert' module, then the uniqueness constraints validation for the Solution Pack is skipped.

0883520

The Elasticsearch service was not starting post-upgrade to 7.3.1. The Elasticsearch service is now accessible following the upgrade to 7.3.2 because this issue has been fixed.

Resolved Issues

Resolved Issues

The following important issues have been fixed in FortiSOAR release 7.3.2. This release also includes important security fixes. To inquire about a particular bug, please contact Customer Service & Support.

Security Fixes

Bug ID Description

0882107, 0883505

Fixes for possible privilege escalations.

0885301

Fixed issues with renewing the Threat Intelligence Management license.

Other Fixes

Bug ID Description

0880816

Groups (blocks) in playbooks were not getting deleted even when a playbook was permanently deleted, i.e., removed from the recycle bin.

0882106

Uniqueness constraint validation was being honored while importing modules in Solution Packs that could cause the import to fail. Now, the uniqueness constraint validation in the case of modules in Solution Packs is skipped. For example, if an existing 'Alert' module has uniqueness constraint defined on 'Source' and 'SourceID' fields and you import a solution pack with uniqueness constraint defined on 'SourceID' and 'Name' fields for the 'Alert' module, then the uniqueness constraints validation for the Solution Pack is skipped.

0883520

The Elasticsearch service was not starting post-upgrade to 7.3.1. The Elasticsearch service is now accessible following the upgrade to 7.3.2 because this issue has been fixed.