--------------------------------------------------------------------------------
Forcepoint Email Security v8.5.3


Release Notes for Hotfix 013:    Fixes for Forcepoint Email Security appliance and Management Server


Release Notes updated:           18 September 2020

--------------------------------------------------------------------------------

Contents

     A. Release Notes for Hotfix 013
     B. Hotfix 013 package contents
     C. Installation & configuration (with CLI on V Series, X Series, or 
        virtual appliance)
     D. Verification of back-end version after successful install (V Series, X Series,
        or virtual appliance)
     E. Management Server (Windows) installation
     F. Security Vulnerability Mitigation
     G. Technical Support

--------------------------------------------------------------------------------

A.  Release Notes for Hotfix 013

--------------------------------------------------------------------------------

This hotfix provides the following changes:

1. Supported file types for file sandboxing have been updated.
2. Efficacy of Yara scanning has been improved. (EI-21262)
3. The fix for customer issue #26 was corrected. (EI-22963, EI-22584)
4. The fix for customer issue #45 was corrected. (EI-23984, EI-23981)
5. Yara was changed to support OpenSSL-dependent features so that certain new rules 
   can be deployed. (EI-24193)
6. An improvement was integrated to a library Yara depends on, to improve 
   efficacy of scanning. (EI-14715)
7. The library responsible for communication between the appliance and 
   manager has been updated to support and operate using modern ciphers. (ESG-14693)
8. A log rotation rule has been corrected for certain log files. (ESG-14769)

This hotfix resolves the following customer issues:

1. DomainKeys Identified Mail was not signed correctly for an empty sender 
   when one or more signing rules were defined. (EI-17745)
2. libopendkim, the library used to verify DKIM results, did not handle
   white-space folded headers correctly. As a result, the Antispoof filter did not
   perform as expected. (EI-18102)
3. URL analysis of a message containing an iCalendar content type resulted in 
   miscategorization of the URL, which caused the message to be quarantined 
   as malicious. (EI-18608)
4. Buffer overflow vulnerability was found in Filtering Service. (SVM-2776)
5. A bug affected the way certain SPF records are processed, which
    caused a crash and displayed an alert in Forcepoint Security
    Manager regarding unexpected listcheck restarts. (EI-20433)
6. Queues were unable to use a Samba storage location if the target server had
   SMBv1 disabled and SMBv2 enabled. (EI-20533)
7. Large messages with calendar attachments caused Filtering Service to crash. (EI-20470)
8. There was a vulnerability with the Forcepoint Secure Messaging reset password
   process. If the reset password link was no longer valid, user interface
   elements could be manipulated from the client side to reset the account
   password. (SVM-2588)
9. A design flaw in the Hybrid Service registration process temporarily exposed 
   users to a vulnerability in which an external offender was able to send email 
   on behalf of the protected domain. The exposure window existed between the 
   completion of the "Delivery Route" portion of the Hybrid service 
   registration process and the completion of the Hybrid Service registration 
   process. (EI-20570)
10. The SIEM daemon treated mixed-case and lowercase recipients as different recipients, causing
    policy logs to time out and have missing information. (EI-20118)
11. The DMARC daemon crashed when sending an aggregate report to a domain that had an invalid DMARC
    record. (EI-20808)
12. If an email message was quarantined by DLP and a disclaimer filter was configured, the disclaimer filter
    was ignored. (EI-20572)
13. When Personal Email Manager was accessed via hyperlinks in the notification email summarizing
    quarantined mail, the body of the quarantined mail was displayed without formatting. (EI-20451)
14. When an email was encrypted using S/MIME, an action to use a different mail route was not taken
    unless the action also used header modification. (EI-19551)
15. Password-protected archives were incorrectly classified as unencrypted when
    they contained a folder. (EI-20881)
16. Unfolding was skipped for large calendar invites, so URLs within the invites may have been
    misinterpreted. (ESG-14298)
17. Certain server processes reached an insufficient number, resulting in Antivirus
    filter slowdown and delayed mail. (EI-17200)
18. In Message Log Search in Forcepoint Security Manager, log export displayed an error when searched on
    conditions such as "is" and "does not contain" for recipient address, sender address,
    and analysis result fields. (EI-19665)
19. Message Log Search in Forcepoint Security Manager performed sluggishly. (EI-19706 / EI-19144)
20. When exported from Forcepoint Security Manager, Message Logs containing rejected connections 
    showed analysis result as "Waiting for message analysis" and message status as 
    "Waiting for delivery". (ESG-13857)
21. When using Advanced File Analysis, scanning results for archive files were 
    not properly queried from the Advanced Malware Detection module, resulting 
    in emails with archive attachments not being delivered. 
    (EI-19394)
22. Enhanced logging was enabled as a default for Linking Service and its log file set up to be rotated. (EI-22128)
23. Database partitions appeared in the wrong order. (EI-20558)
24. The CSV export of Message Logs contained extra lines between results, when results whose 
    quoted-printable encoding of the subject spanned multiple lines. (EI-20748)
25. Unnecessary DMARC checks occurred for messages that were released from DLP. (EI-21656)
26. A restart of SSLProxy, normally invoked during an appliance backup, caused the Java process to stop 
    if there was prior communication between members of a cluster via SSLProxy. (EI-21443 / EI-17454)
27. The display name, or friendly name, was not parsed correctly when it contained apostrophes or 
    parentheses. This caused equality checks between "From:" address and envelope address to fail. 
    (EI-21708)
28. If TLS encryption was used as a primary encryption method, and secure message delivery 
    was used as a backup encryption method, the secure message recipient was unable to use 
    the Reply All, Forward, Compose, or Attach Files features even if they were enabled. (EI-22048)
29. LogDaemon created many entries and filled up the directory "/var/log/logdaemon_err" 
    as a result of the connection logs containing incomplete information, due 
    to a bug related to communication with Office 365. (EI-22026)
30. When creating a user directory of the type "Active Directory", only up to 50 users under the 
    ProxyAddresses attribute were fetched due to a limitation in AuthDaemon, which caused 
    other users to fail to authenticate. This fix increases the supported address 
    limit from 50 to 1000. (EI-22382)
31. Downloading quarantined mail from Personal Email Manager stopped working in 
    Google Chrome after the browser updated to version 75. (EI-22243)
32. ConfigDaemon logs showed plaintext SQL Server password when failing to connect to SQL Server.
    (EI-22630)
33. Message log export had incorrect results when searched with "From:header" and "To:header". (EI-22429)
34. When messages were blocked due to a connection check that generates a Message Log, such as 
    authentication failures, TSIP, SPF, RDNS, or RBL, a Policy Log was mistakenly queued.
    (EI-22585)
35. Changes to Recipient List user's password while in filtered view caused loss of users. (EI-22386)
36. Connection logs and connection details in Message Logs showed TLS connections as non-TLS. 
    (EI-21545)
37. The SMTP reply portion of the delivery logs was vulnerable to XSS attacks. (SVM-3176)
38. There was a page formatting issue within the hybrid registration wizard when viewing 
    CNAME verification results after deleting a delivery route. (EI-22768)
39. The Personal Email Manager user interface for Always Block List and Always Permit List 
    displayed incorrect text when trying to add a sender who was already present in either list.
    Additionally, it was possible to add the same sender to both lists. (EI-23003)
40. If Forcepoint Secure Messaging security question answers contained diacritics, the
    diacritics were saved as question marks. Without knowing this and doing a character
    substitution, it was impossible for some users who forgot their password to change it. (EI-22866)
41. In some scenarios, the DKIM result was not displayed in the Message Log or was displayed 
    in a confusing way. (EI-22682)
42. Diacritics in the subject line were corrupted by the Forcepoint Secure Messaging portal. (EI-22442)
43. The encryption upgrade of proxy passwords, which was invoked during an upgrade to version 8.5.3, 
    mistakenly encrypted blank passwords. A mismatch of encrypted passwords between the primary and 
    secondary nodes of a cluster caused the Filtering Service of the secondary node to constantly restart. 
    (EI-22649)
44. Copying an Advanced File Analysis filter did not copy the selected file types of the original 
    filter. (EI-23082)
45. Poor network conditions could have caused the remote queue count and size recalculation 
    procedure done at initialization to hang indefinitely. Consequently, the task responsible 
    for cleaning up queues to match retention settings was not able to run. (EI-23145)
46. The blocked messages page of Forcepoint Security Manager was unable to display messages 
    blocked by Data Loss Prevention if those messages were the only type of blocked messages 
    in the given time range. (ESG-14558)
47. When multiple SMTP servers were listed, removing a higher priority SMTP server and 
    simultaneously trying to edit a lower priority SMTP server resulted in an error. (ESG-14442)
48. Log export displayed incorrect results when more than one search condition was used, 
    in addition to an Advanced Search based on direction. (EI-23572 / EI-23553)
49. Caching of IP information attained by querying the Appliance API has been added 
    to address potential slowdowns when navigating Forcepoint Security Manager. (ESG-14432)
50. Some attachments with non-ASCII filenames that were sent for Advanced File Analysis 
    may have caused messages to end up in the exception queue due to inconsistencies
    with encoding and decoding. (EI-24022)
51. Caching has been disabled on pages within Personal Email Manager containing sensitive 
    information. (SVM-3256)
52. The lack of HELO information during the SPF verification stage of email processing 
    for hybrid mail caused mail from certain domains to fail SPF validation. (EI-23913)
53. Telephone-number links within messages were classified as "Uncategorized" via 
    URL Analysis if the category Miscellanous > Uncategorized was selected. (EI-24060)
54. Exporting of message logs exported more data than was displayed. (ESG-14615)
55. Size statistics for remote queues were over-represented. (ESG-14583)
56. Buttons on the Quarantined Messages page within Personal Email Manager were displayed 
    incorrectly if the the browser window width was below a certain amount. This also occurred 
    on the Blocked Messages page within Forcepoint Security Manager. (ESG-14544)
57. The "More Actions" button, present on various pages within Forcepoint Security Manager, 
    Personal Email Manager, and Forcepoint Secure Messaging, was displayed incorrectly. (ESG-14518)
58. Diacritic characters were incorrectly displayed in the body of Forcepoint Secure Messaging 
    messages for some encodings. (ESG-14500)
59. The functions within the Forcepoint Email Security command-line interface intended 
    to restrict the incoming or outgoing mail transfer agent TLS levels were not working 
    as expected. It was previously impossible to restrict communication to only TLS 1.2, 
    and certain combinations of usage resulted in an unencrypted connection. (ESG-14607)
60. True Source IP was not considered in a hybrid configuration for messages rejected 
    by DMARC. This led to incorrect IP information displayed in connection logs. Additionally, 
    incorrect sender IP information propagated to aggregate DMARC reports. (EI-24069 / EI-24070)
61. Validation was inadequate for addresses to which DMARC aggregate reports are sent. (EI-24483 / EI-23748)
62. When a large number of hybrid domains was used, adding another route caused a crash and the route was not added. (EI-19506)
63. It was not possible to specify a body signing length of 0 for DKIM signing rules. (EI-24984)
64. The maximum number of log database partitions was previously limited to 32767. (EI-25472)
65. Support for Thai character set "windows-874" was missing from Forcepoint Secure Messaging. (EI-25425)
66. Certain invalid DMARC records caused coredumps of name "core_cleanup" to be produced 
    as a result of a bug within the library related to parsing DMARC records. (EI-25047)
67. Archive files scanned by Advanced File Analysis were treated as exceptions with no report link shown, 
    regardless of whether the files were malicious. The root cause, which has been fixed,
    was that the changes in EI-24022 were not applied for archive files. (ESG-24894)
68. Disabling TLSv1.0 for incoming or outgoing mail via the Forcepoint Email Security command-line interface did not 
    automatically enable TLSv1.1 and TLSv1.2, which caused mail delivery issues. (ESG-14618)
69. DMARC's DKIM alignment check failed in many scenarios where a message contained multiple 
    DKIM signatures because not all DKIM signatures were checked against. (EI-25529)
70. When a Forcepoint Security Manager administrator belonged to multiple network groups with and without 
    access to the email module, a network server error occurred when navigating to the Email tab. (EI-24658)
71. Mail for which DMARC verification was performed caused fatal unknown transport errors and mail delays 
    due to an extraneous quotation mark character in the sender's DNS record. (EI-26384)
72. A race condition existed when accessing the shared memory containing encryption tokens, which potentially 
    caused filter crashes. (ESG-14886)
73. Microsoft's unquoted service path enumeration security vulnerability has been addressed by 
    encapsulating the paths of the LogServer and STunnel services within quotation marks. (SVM-3394)
74. Intermittently, AMD message logs stayed in the Delayed Queue for messages that were already delivered. (EI-26278)
75. Within Personal Email Manager, clicking on the "More Actions" button in the messages view took the user back 
    to the Quarantined Message page rather than allowing the user to select an action. (ESG-14790) 


This hotfix adds the following features:

1. A new CLI command that enables filter actions to use the True Source IP of
   a message in header modifications. (ESG-14217)
2. A new CLI command that disables or enables native load balancing for Forcepoint Secure Messaging
   and Personal Email Manager components, which is done via HAProxy. This feature is
   intended for users utilizing an alternate load balancing solution. (EI-20966)

--------------------------------------------------------------------------------

B.  Hotfix 013 package contents

--------------------------------------------------------------------------------

Linux components:

A package in .rpm format (Appliance-Hotfix-Email-8.5.3-013.rpm) contains 1 file
with fixes to the following component:

- Forcepoint Email Security Appliance

Windows components:

A package in .zip format (Email-8.5.3-013.rpm) contains automated installation
batch scripts with fixes to the following components:

- Forcepoint Security Manager
- Forcepoint Email Security Log Database


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

                            IMPORTANT

You must install all hotfix components for proper system operation. 
Install the appliance and Windows components in the order indicated below. 
Communication between your email appliance and Forcepoint Security Manager is 
interrupted until hotfix installation is complete on all components.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Be sure to back up your Forcepoint Email Security configuration before you 
apply this hotfix. See the following link for details:

http://www.websense.com/content/support/library/shared/v85/backup_faq/first.aspx 

After installation of each component, restart each service.

This hotfix is valid for users of Forcepoint Email Security v8.5.3 
(appliance v8.5.3).

-------------------------------------------------------------------------------

C. Installation & configuration (with CLI on V Series, X Series, or 
   virtual appliance)

-------------------------------------------------------------------------------

Use the Command Line Interface to install the hotfix.
It is advisable to have assistance from Forcepoint Technical Support.
Optionally, you can install appliance hotfixes using FSAM via the bulk hotfix installer or the Software Updates tab.

1.  Log on to the appliance as admin user.

2.  Enter config mode.

3.  Execute the following command:

      show hotfix list

4.  Locate the ID Email-8.5.3-013 from the list displayed by the command 
    in step 3, and then execute the following command:

      load hotfix --id Email-8.5.3-013

5.  Install the hotfix by executing the following command:

      install hotfix --id Email-8.5.3-013

6.  In the event that you wish to uninstall the hotfix, run the following 
    command:

      uninstall hotfix --id Email-8.5.3-013

------------------------------------------------------------------------------

D.  Verification of back-end version after a successful installation (V Series, 
    X Series, or virtual appliance)

------------------------------------------------------------------------------

Open the file '/usr/local/etc/esg.version' and check for an entry of
'hotfix_number'.

If you see 'hotfix_number=13', the hotfix was installed successfully.

Continue installing the Windows components in the next section. 

------------------------------------------------------------------------------

E. Management Server (Windows) installation

------------------------------------------------------------------------------

===============================================================================
Forcepoint Management Server (Windows) installation
===============================================================================
1. Unpack the file Email-8.5.3-013.zip. Launch 
   install_manager.bat or run it from command-line prompt for automated 
   installation. Alternatively, read the following instructions for manual 
   installation.
2. Use the Forcepoint Management Server default installation path (C:\Program Files(x86)\Websense) or your own installation 
   path.
3. Stop the Websense TRITON - Email Security Service as follows:
   a. Go to the Service Control Manager
      (Start > Control Panel > Administrative Tools > Services).
   b. Locate and stop the Websense TRITON - Email Security service. 
4. Navigate to the following directory:
   C:\Program Files (x86)\Websense\Email Security\ESG Manager\tomcat\esg\
   a. Rename the existing ConfigUI.war file to ConfigUI.war.pre-HFXX.bak.
   
   b. Extract the WH-Manager-8.5.3-013.zip archive, and copy and paste the new
      ConfigUI.war file into this directory.
5. Delete the following directories:
   a. C:\Program Files (x86)\Websense\Email Security\ESG Manager\tomcat\webapps\esg
   b. C:\Program Files (x86)\Websense\Email Security\ESG Manager\tomcat\work\Catalina
   
6. Start the Websense TRITON - Email Security service as follows:
   a. Go to the Service Control Manager
      (Start > Control Panel > Administrative Tools > Services).
   b. Locate and start the Websense TRITON - Email Security service.
7. Check that the hotfix was successfully installed as follows:	
    a. Verify that you can log in to Forcepoint Security Manager.
	
	
===============================================================================
Email Security Log Database Installation (Windows)
===============================================================================
Use the following steps to install the Forcepoint Email Security Log Database 
hotfix on your Email Log Server machine:
1. Unpack the file Email-8.5.3-013.zip.
2. Install the Email Log Database hotfix using the default 
   installation path (C:\Program Files (x86)\Websense) or your own 
   installation path.
3. Open a Windows Command Prompt window (Start > All Programs > Accessories > 
   Command Prompt), navigate to the directory where
   Email-8.5.3-013.zip was extracted, and execute the
   following command:
      install_database.bat 
4. Check that the hotfix was successfully installed. Ensure that no errors 
   appear in the output files in the following location: 
   C:\Program Files (x86)\Websense\Email Security\ESG Log Server\SQL\Hotfix013
   \hotfix_install.txt

If needed, use the following steps to uninstall the Email Log 
Database hotfix. Please be aware that uninstalling database changes reverts 
database stored procedures to release level, so be sure to reinstall any 
necessary database fixes that were released between the release level and your 
target hotfix level:

1. Uninstall the Email Log Database hotfix using the default installation 
   path (C:\Program Files (x86)\Websense) or your own installation path.
2. Open a Windows Command Prompt window (Start > All Programs > Accessories > 
   Command Prompt), navigate to the directory where
   Email-8.5.3-013.zip was extracted, and execute the
   following command:
   
      install_database.bat rollback
3. Check that the hotfix was successfully uninstalled. Ensure that no errors 
   appear in the output files in the following location: 
   C:\Program Files (x86)\Websense\Email Security\ESG Log Server\SQL\Hotfix013
   \hotfix_install.txt


-------------------------------------------------------------------------------

F.  Security Vulnerability Mitigation

-------------------------------------------------------------------------------   
   
1. The script "Windows_Path_Enumerate.ps1" to resolve the Microsoft unquoted 
   service path enumeration vulnerability has been included within the Windows 
   archive and inside the archive named UnquotedServicePathsMitigation.zip. The
   affected Forcepoint services are LogServer and STunnel. To resolve the 
   vulnerability, please run the script on the Windows system(s) containing 
   the affected services. In the vast majority of deployments, this will only
   be the Forcepoint Security Manager server. (CVE-2013-1609, CVE-2014-0759,
   CVE-2014-5455) 
   Script Source and Release Notes: 
   https://gallery.technet.microsoft.com/scriptcenter/Windows-Unquoted-Service-190f0341
   
-------------------------------------------------------------------------------

G.  Technical Support

-------------------------------------------------------------------------------

Technical information about Forcepoint products is available 24 hours a 
day at:

   	http://support.forcepoint.com 

         	 - tips
                 - customer forums
                 - latest release information
                 - searchable Knowledge Base 
                 - latest hotfixes and patches
                 - show-me tutorials and videos
                 - product documents
                 - answers to frequently asked questions
         	 - in-depth technical papers
                 - monthly support webinars
                 - technical alerts
                 - most popular solutions 

The Support site offers access to all technical resources, including opening 
a case via the Service Request portal.

------------------------------------------------------------------------------

(c) 1996-2020 Forcepoint LLC. All rights reserved.

Trademarks

Forcepoint is a trademark of Forcepoint LLC. SureView, TRITON, ThreatSeeker, 
Sidewinder, and Stonesoft are registered trademarks of Forcepoint LLC. 
Raytheon is a registered trademark of Raytheon Company. Forcepoint has 
numerous other unregistered trademarks in the United States and 
internationally. All other trademarks are the property of their respective 
owners.
