Release Notes

Dashboard and processing history of Metadefender ICAP Server can be viewed on My OPSWAT and on Central Management v8 from this version (v5.7.0)

• Beside SOAP/JSON format, MD ICAP Server v5.7.0 has already supported extracted and scanned base64 data which is embedded in FORM URL Encoded
• Able to select the node/path to specific the file name for Base64 data, this will help trace back the scan data at MD Core side more easier
• Support configure to select scan all base64 data in array at once (use "*"), instead of configure each node one by one

More detail, refer to Content encoded (SOAP/JSON/Form URLEncoded)

MetaDefender ICAP Server now bundle the PostgreSQL database v16.x. With this upgrade, the MetaDefender ICAP Server can support remote PostgreSQL from v12.x to v17.x

Important: The product does not upgrade the customer's remote PostgreSQL version.

Refer to Upgrade to MetaDefender ICAP Server v5.7.0 or newer

The Client IP (represented by X-CLIENT-IP header) and UserName (represented by UserName header) on processing history can be overridden by any header value

The Metadata of each scan can be used to trace back the source of requests, Metadefender ICAP Server is supporting to select one of multiple header value as a metadata for scan request.

Upgraded third-party libraries for vulnerability fixes:

• Curl v8.9.1 (Windows)
• Qt v6.7.2
• Npgsql 4.0.17
• PostgreSQL v16.6

Front-end enhancements:

• Upgrade to Angular v17

• Enhance the license management to align with new update of On-Premises License Management Server (OLMS).
• Added smaller options to Data Retention settings
• Support 2 new service paths for Globalscape's EFT integration
• Support new content encoding: zstandard - zstd

• Windows Server 2012: Microsoft has ended support for Windows Server 2012 as of October 2023. Reference
• Debian 9 has been unsupported since June 2022

MetaDefender ICAP Server version 5.7.0 will no longer support these OS versions. We recommend that customers migrate their systems to newer and supported versions of Windows Server.

For a list of currently supported Windows OS versions, refer to Operating Systems.

In MetaDefender ICAP Server v5.5.0, users cannot create a new SAML directory via the web UI.

• Workaround: Use the REST API to create the SAML directory.
• Impact: Existing SAML directories are not affected when upgrading to MetaDefender ICAP Server v5.5.0
• Resolution: This issue is resolved in MetaDefender ICAP Server v5.5.1 or newer.

MetaDefender ICAP Server 5.1.0 or newer may encounter stability issues on Red Hat /Cent OS systems running kernel version 372.

Solution: Red Hat has addressed this issues in the latest kernel version 425

In MetaDefender ICAP Server v5.1.0 or newer, OpenSSL 1.x has been replaced with OpenSSL 3.x within the product and other dependencies to enhance security and address vulnerabilities.

NGINX's OpenSSL 3.x on MetaDefender ICAP Server has the enforcement in place to reject all weak cipher suites. The web server only accepts "HIGH" encryption cipher suites https://www.openssl.org/docs/man1.1.1/man1/ciphers.html (MD5 and SHA1 hashing based are also not accepted).

As a result, if you already configured MetaDefender ICAP Server for HTTPS using a weak SSL cipher with your certificate, the server will not start due to NGINX's OpenSSL 3.x enforcement.

MetaDefender ICAP Server v5.1.0 on Debian OS must execute the two following commands to enable TLS when connecting to MetaDefender Core.

sudo mkdir -p /etc/pki/tls/certs/

sudo ln -s /etc/ssl/certs/ca-certificates.crt /etc/pki/tls/certs/ca-bundle.crt

Resolution: This issue is fixed in MetaDefender ICAP Server v5.1.1