Secure Web Gateway 11.2.2 Release Notes

New Features in the 11.2 Release

This release provides the following new features. For resolved issues in this release and the update releases, see further below.

NOTE: Secure Web Gateway 11.2 is provided as a main release.

For information about how to install this release, see the Upgrading to a New Version - Controlled Release. If you are installing the Secure Web Gateway appliance software for the first time, see Installing Secure Web Gateway for the First Time.

When configuring rules for your web policy, you can use these new items:

A new property to expose encrypted archive directory listings.
A new property to store the rule and rule set names or IDs that were processed at the end of the request and response filtering cycles.

Data that is collected by the GTI diagnosis script of the operating system is included in the output feedback file.

Support for rolling TCPdump collection option is now available in the UI. For more details, see Create a packet tracing file. For more details on Performing Packet Tracing in Secure Web Gateway, see Performing Packet Tracing in Secure Web Gateway SWG

When configuring an HTTP Proxy Port, you can disable the Enable FTP over HTTP option. The option is enabled by default.

The following enhancements have been added to SSL Tap configuration:

The destination port number is not overwritten by default when tapped packets are created.
The destination MAC address can be customized when tapped packets are broadcast.
SSL tapping now supports HTTP2 on Secure Web Gateway.

Excel 4 macros are now detected in media type filtering.

IP spoofing is supported for HTTP(S) when setting up proxies in Explicit Proxy or L2 Transparent mode.

For a list of issues that are currently known, see SWG 11.x.x Known Issues and Workaround

This release resolves known issues.

NOTE: Secure Web Gateway 11.2.2 is provided as a main release.

For information about how to upgrade to this release, see Upgrading to a new version – Main Release.

JIRA issue numbers are provided in the reference columns.

Other

Reference	Description
WP-4767	Resolved SWG not processing traffic issue when used along with HSM , due to threads hanging in critical section lock.
WP-4813	Alerts related to HSM keys containing control characters are escaped (‘%’ replaced with ‘/’) to resolve Alert Page disappear issue.
WP-4833	Secure Web Gateway on-prem forwards all requests with X-SWEB headers to Secure Web Gateway cloud again.
WP-4836	The client_ip field in the access log for Secure Web Gateway cloud no longer omits the IP address of Secure Client Proxy.
WP-4839	The AOLE2 Opener used for opening Microsoft Office files does not crash anymore.

Vulnerabilities Fixed

Reference

Description

WP-4801, WP-4802, WP-4834, WP-4841

This Secure Web Gateway release includes updates addressing publicly disclosed CVEs, regardless of whether a CVE has been shown to impact customers.

The following medium and higher-level CVEs (CVSS 3.0 >= 4) were involved:

CVE-2020-10663 - There is no impact on SWG. The ruby core of SWG does not use this library to parse/process JSON data, so there is no input vector available for exploitation.
CVE-2021-31799 - There is no impact on SWG. Since package is used to generate documentation and is therefore not installed on customer environments.
CVE-2020-26116 - There is no impact on SWG, since Python is not in use for normal SWG functioning.
CVE-2020-26137
CVE-2022-0391
CVE-2022-34169 - There is no impact. SWG does not load untrusted code.
CVE-2022-25647
CVE-2022-21541
CVE-2022-21540
CVE-2022-21549

For more information about these CVEs and their impact, see the Red Hat CVE portal.