Juniper Secure Analytics Release Notes

Installing the JSA 7.3.3 Fix Pack 7 (Patch 7) Software Update

JSA 7.3.3 Fix Pack 7 (Patch 7) resolves reported issues from users and administrators from previous JSA versions. This cumulative software update fixes known software issues in your JSA deployment. JSA software updates are installed by using an SFS file. The software update can update all appliances attached to the JSA Console.

The 7.3.3.20210111145446 SFS file can upgrade JSA 7.3.1 or JSA 7.3.2 to JSA 7.3.3 Fix Pack 7 (Patch 7). This document does not cover all installation messages and requirements, such as changes to appliance memory requirements or browser requirements for JSA. For more information, see the Juniper Secure Analytics Upgrading JSA to 7.3.3.

Precautions

• Back up your data before you begin any software upgrade. For more information about backup and recovery, see the Juniper Secure Analytics Administration Guide.
• To avoid access errors in your log file, close all open JSA webUI sessions.
• The software update for JSA cannot be installed on a managed host that is at a different software version from the Console. All appliances in the deployment must be at the same software revision to update the entire deployment.
• Verify that all changes are deployed on your appliances. The update cannot install on appliances that have changes that are not deployed.
• If this is a new installation, administrators must review the instructions in the Juniper Secure Analytics Installation Guide.

Installation Steps

1. Download the 7.3.3.20210111145446 SFS from the Juniper Customer Support website: https://support.juniper.net/support/downloads/
2. Using SSH, log into your system as the root user.
3. To verify you have enough space (5 GB) in /store/tmp for the JSA Console, type the following command:
   

   df -h /tmp /storetmp /store/transient | tee diskchecks.txt

   • Best directory option: /storetmp
     It is available on all appliance types at all versions. In JSA 7.3.0 versions, /store/tmp is a symlink to the /storetmp partition.
   • 2nd best directory option: /tmp
     This directory is available on all appliances, but in 7.3.0 versions, it is significantly smaller, and moving a file here can cause services to stop. If you leave a file in /tmp for 10 days without completing the SFS update, it might get cleaned up by Red Hat's tmpwatch cron job.
   • 3rd best option: /store/transient
     The /store/transient directory was introduced in JSA 2014.1 and is allocated 10% of the overall /store directory. However, this directory does not exist on all appliances and might not be an actual partition on all appliances.

   If the disk check command fails, retype the quotation marks from your terminal, then re-run the command. This command returns the details to both the command window and to a file on the Console named diskchecks.txt. Review this file to ensure that all appliances have at minimum 5 GB of space available in a directory to copy the SFS before attempting to move the file to a managed host. If required, free up disk space on any host that fails to have less than 5 GB available.

   NOTE: In JSA 7.3.0 and later, an update to the directory structure for STIG compliant directories reduces the size of several partitions. This can impact moving large files to JSA.

4. To create the /media/updates directory, type the following command:
   

   mkdir -p /media/updates

5. Using SCP, copy the files to the JSA Console to the /storetmp directory or a location with 5 GB of disk space.
6. Change to the directory where you copied the patch file. For example, cd /storetmp
7. Unzip the file in the /storetmp directory using the bunzip2 utility:
   

   bunzip2 7.3.3.20210111145446.sfs.bz2

8. To mount the patch file to the /media/updates directory, type the following command:
   

   mount -o loop -t squashfs /storetmp/7.3.3.20210111145446.sfs /media/updates

9. To run the patch installer, type the following command:
   

   /media/updates/installer

Installer Options

NOTE: The first time that you run the software update, there might be a delay before the software update installation menu is displayed.

1. Using the patch installer, select all.
   • The all option updates the software on all appliances in the following order:
     • Console
     • No order required for remaining appliances. All remaining appliances can be updated in any order the administrator requires.
   • If you do not select the all option, you must select your console appliance.

   As of the JSA 2014.6.r4 patch and later, administrators are only provided the option to update all or update the Console appliance. Managed hosts are not displayed in the installation menu to ensure that the console is patched first. After the console is patched, a list of managed hosts that can be updated is displayed in the installation menu. This change was made starting with the JSA 2014.6.r4 patch to ensure that the console appliance is always updated before managed hosts to prevent upgrade issues.

   If administrators want to patch systems in series, they can update the console first, then copy the patch to all other appliances and run the software update installer individually on each managed host. The console must be patched before you can run the installer on managed hosts. When updating in parallel, there is no order required in how you update appliances after the console is updated.

   If your Secure Shell (SSH) session is disconnected while the upgrade is in progress, the upgrade continues. When you reopen your SSH session and rerun the installer, the patch installation resumes.

Installation Wrap-up

1. After the patch completes and you have exited the installer, type the following command:
   

   umount /media/updates

2. Clear your browser cache before logging in to the Console.
3. Delete the SFS file from all appliances.

Results

A summary of the software update installation advises you of any managed host that were not updated. If the software update fails to update a managed host, you can copy the software update to the host and run the installation locally.

After all hosts are updated, administrators can send an email to their team to inform them that they will need to clear their browser cache before logging in to the JSA.

Clearing the Cache

After you install the patch, you must clear your Java cache and your web browser cache before you log into the JSA appliance.

Before you begin

• Ensure that you have only one instance of your browser open. If you have multiple versions of your browser open, the cache might fail to clear.
• Ensure that the Java Runtime Environment is installed on the desktop system that you use to view the user interface. You can download Java version 1.7 from the Java website: http://java.com/.

About this task

If you use the Microsoft Windows 7 operating system, the Java icon is typically located under the Programs pane.

To clear the cache:

1. Clear your Java cache:
   1. On your desktop, select Start > Control Panel.
   2. Double-click the Java icon.
   3. In the Temporary Internet Files pane, click View.
   4. On the Java Cache Viewer window, select all Deployment Editor entries.
   5. Click the Delete icon.
   6. Click Close.
   7. Click OK.
2. Open your web browser.
3. Clear the cache of your web browser. If you use the Mozilla Firefox web browser, you must clear the cache in the Microsoft Internet Explorer and Mozilla Firefox web browsers.
4. Log in to JSA.

Known Issues and Limitations

None.

Resolved Issues

The following are the resolved issues addressed in the JSA 7.3.3 Fix Pack 7 (Patch 7):

• CVE-2019-19126, CVE-2020-10754, CVE-2019-19956, CVE-2019-20388, CVE-2020-7595, CVE-2019-5482, CVE-2018-20843, CVE-2019-15903, CVE-2019-20386, CVE-2019-16935, CVE-2020-8492, CVE-2019-17498, CVE-2019-2974, CVE-2020-2574, CVE-2020-2752, CVE-2020-2780, CVE-2020-2812, CVE-2019-14907, AND CVE-2019-14866-JSA IS VULNERABLE TO USING COMPONENTS WITH KNOWN VULNERABILITIES.
• CVE-2018-18074, CVE-2018-20060, CVE-2019-11236, CVE-2019-11324, CVE-2019-5094, CVE-2019-5188, CVE-2020-11008, CVE-2019-12450, CVE-2019-14822, CVE-2019-14973, CVE-2019-17546, CVE-2017-15715, CVE-2018-1283, CVE-2018-1303, CVE-2019-10098, CVE-2020-1927, CVE-2020-1934, CVE-2017-18551, CVE-2018-20836, CVE-2019-15217, CVE-2019-15807, CVE-2019-15917, CVE-2019-16231, CVE-2019-16233, CVE-2019-16994, CVE-2019-17053, CVE-2019-17055, CVE-2019-19046, CVE-2019-19062, CVE-2019-19063, CVE-2019-19332, CVE-2019-19447, CVE-2019-19524, CVE-2019-19530, CVE-2019-19534, CVE-2019-19537, CVE-2019-19767, CVE-2019-19807, CVE-2019-20054, CVE-2019-20636, CVE-2019-9454, CVE-2019-9458, CVE-2020-10690, CVE-2020-10732, CVE-2020-10742, CVE-2020-10751, AND CVE-2020-10942-JSA IS VULNERABLE TO USING COMPONENTS WITH KNOWN VULNERABILITIES.
• CVE-2019-2974, CVE-2020-2574, CVE-2020-2752, CVE-2020-2780, CVE-2020-2812, CVE-2019-14973, CVE-2019-17546, CVE-2019-17498, CVE-2017-15715, CVE-2018-1283, CVE-2018-1303, CVE-2017-15715, CVE-2018-1283, CVE-2018-1303, CVE-2019-10098, CVE-2020-1927, CVE-2020-1934, CVE-2017-18551, CVE-2019-10098, CVE-2020-1927, CVE-2020-1934, CVE-2019-5094, CVE-2019-5188, AND CVE-2020-0034-JSA IS VULNERABLE TO USING COMPONENTS WITH KNOWN VULNERABILITIES.
• CVE-2020-11979-APACHE ANT AS USED BY JSA IS VULNERABLE TO INSECURE TEMPORARY FILES.
• CVE-2020-4789-JSA IS VULNERABLE TO ARBITRARY FILE READ.
• CVE-2020-4787-JSA IS VULNERABLE TO SERVER SIDE REQUEST FORGERY (SSRF).
• CVE-2020-4786-JSA IS VULNERABLE TO SERVER SIDE REQUEST FORGERY (SSRF).
• CVE-2020-5421-SPRING FRAMEWORK AS USED BY JSA IS VULNERABLE TO IMPROPER INPUT VALIDATION.
• INCORRECT SYSTEM RULE NAME CAN BE RETURNED FROM AN API QUERY AFTER THE RULE HAS BEEN RENAMED AND TOMCAT HAS BEEN RESTARTED.
• JSA ASSET CLEANUP PROCESS CAN FAIL AND GENERATE A PSQLEXCEPTION WHEN ATTEMPTING TO RUN.
• CONTENT MANAGEMENT TOOL IMPORT DEOPTIMIZES CUSTOM PROPERTIES REFERENCED IN A SEARCH FILTER TEST, REDUCING RULE PERFORMANCE.
• FORWARDING NORMALIZED FLOWS THAT ARE ASSOCIATED TO A DOMAIN FAILS WITH A BUFFERUNDERFLOWEXCEPTION WRITTEN TO JSA LOGGING.
• THE OPTION TO USE IPV6 SOURCE AND DESTINATION FROM AN EVENT WHEN CONFIGURING JSON FORWARDING DESTINATION IS NOT AVAILABLE.
• 'FAILED TO MODIFY RX AND TX VALUE FOR ETH0' WHEN INSTALLING JSA ON A KVM THAT IS USING VIRTIO_NET DRIVER.
• 'DEVICE STOPPED EMITTING EVENTS' EVENT CAN DISPLAY INCORRECT LOG SOURCE TIME OF EPOCH 0.
• ATTACHMENTS IN REPORT MAIL CAN BE CORRUPTED AFTER A JSA PATCH HAS BEEN APPLIED.
• LARGE AMOUNTS OF REVERSE DNS LOOKUPS CAN BE GENERATED WHEN OFFLINE ROUTING RULES ARE CONFIGURED IN JSA.
• ARIEL DATA FILE CORRUPTION CAN OCCUR CAUSING "I/O ERROR" DURING SEARCHES WHEN EMAIL RESPONSE TO A SPECIFIC RULE IS CONFIGURED.
• 'THIS INFORMATION SHOULD CONTRIBUTE TO THE NAME OF THE ASSOCIATED OFFENSE' RULE RESPONSE NOT WORKING AS EXPECTED.
• PERFORMING AN EXTENSION MANAGEMENT UNINSTALL CAN SOMETIMES CORRUPT RULES WITHIN JSA.

A JSA Deploy Changes on 31 December 2020 can Impact Product Functionality

A JSA "DEPLOY CHANGES" PERFORMED ON DECEMBER 31 2020 CAN CAUSE JSA FUNCTIONALITY ISSUES. FOR MORE INFORMATION, SEE "A JSA Deploy Changes on 31 December 2020 can Impact Product Functionality” on page 9.

OFFENSE INDEXING ON A CUSTOM EVENT PROPERTY (CEP) THAT HAS A UTF 0X00 (NULL) VALUE CAN CAUSE OFFENSES TO STOP GENERATING.

Urgency

NOTE: JSA development has recently identified a defect in the product licensing function, which may cause the deployment to stop functioning. The JSA development team is currently working on an emergency fix to resolve this issue. Administrators who have automatic updates configured to auto restart or automatically deploy changes after a download might experience service issues. The issue is related to the function that validates a license key and is not related to the reported SolarWinds security issue.

Issue Details

When this issue occurs, the following message might be displayed for specific services in /var/log/qradar.log:

[ecs-ec-ingress.ecs-ec-ingress] [main] com.eventgnosis.ecs: [INFO]
[NOT:6000][X.X.X.X/- -] [-/- -]Waiting for valid license...
[ecs-ep.ecs-ep] [main] com.eventgnosis.ecs: [INFO] [NOT:6000][X.X.X.X/- -] [-/- 
]Waiting for valid license...
[ecs-ec.ecs-ec] [main] com.eventgnosis.ecs: [INFO] [NOT:6000][X.X.X.X/- -] [-/- 
]Waiting for valid license...

If you note repeated information messages in the logs or service issues, run the command documented in this technical note to resolve the issue.

Affected Products

All JSA releases are affected by this issue.

NOTE: If you upgrade to a JSA release prior to the release of JSA 7.3.3 Fix Pack 7, you must reapply the workaround documented in this flash notice.

How to Resolve the Issue

Juniper Support is alerting all administrators to complete the provided single-line command workaround on the JSA Console. If you have received a JAR file from Juniper Support or already received assistance, you must still complete this procedure. After the command is run, administrators can wait for 5 minutes and verify that events are being sent from appliances.

1. Use SSH to log in to the JSA Console as the root user.
2. To update the license file, select the following command. You can double-click the command to highlight and copy the full text from this technical note.
   1. For JSA Consoles.

   NOTE: The all_servers command allows the Console appliance to update all managed hosts.

   /opt/qradar/support/all_servers.sh -Ck 'if [ -f /opt/qradar/ecs/license.txt ] ; then echo -n "QRadar:Q1 Labs
   Inc.:0007634bda1e2:WnT9X7BDFOgB1WaXwokODc:12/31/20" > /opt/qradar/ecs/license.txt ; fi ; if [ -f
   /opt/ibm/si/services/ecs-ec-ingress/current/eventgnosis/license.txt ] ; then echo -n "QRadar:Q1 Labs Inc.:0007634bda1e2:WnT9X7BDFOgB1WaXwokODc:12/31/20" >
   /opt/ibm/si/services/ecs-ec-ingress/current/eventgnosis/license.txt ; fi ; if [ -f /opt/ibm/si/services/ecs-ep/current/eventgnosis/license.txt ] ; then echo -n "QRadar:Q1 Labs Inc.:0007634bda1e2:WnT9X7BDFOgB1WaXwokODc:12/31/20" > /opt/ibm/si/services/ecs-ep/current/eventgnosis/license.txt ; fi ; if [ -f /opt/ibm/si/services/ecs-ec/current/eventgnosis/license.txt ] ; then echo -n "QRadar:Q1 Labs Inc.:0007634bda1e2:WnT9X7BDFOgB1WaXwokODc:12/31/20" > /opt/ibm/si/services/ecs-ec/current/eventgnosis/license.txt ; fi ; if [ -f /usr/eventgnosis/ecs/license.txt ] ; then echo -n "QRadar:Q1 Labs Inc.:0007634bda1e2:WnT9X7BDFOgB1WaXwokODc:12/31/20" > /usr/eventgnosis/ecs/license.txt ; fi ; if [ -f /opt/qradar/conf/templates/ecs_license.txt ] ; then echo -n "QRadar:Q1 Labs Inc.:0007634bda1e2:WnT9X7BDFOgB1WaXwokODc:12/31/20" > /opt/qradar/conf/templates/ecs_license.txt ; fi'

3. Wait 5 minutes for the changes to complete.

NOTE: Administrators are not required to restart any services for this change as the file loads automatically.

4. Log in to the JSA Console.
5. Click the Log Activity tab.
6. Verify events are received from remote appliance.

Results

The procedure is complete. If you upgrade your JSA release prior to the release of JSA 7.3.3 Fix Pack 7, you must reapply the workaround to the JSA Console. If you experience an issue with this command or continue to experience services or license messages in qradar.log, contact Juniper Support for assistance. After you apply the workaround for this issue, you can use JSA normally and complete standard administrative tasks, such as deploy changes.

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can provide feedback by using either of the following methods:

• Online feedback system—Click TechLibrary Feedback, on the lower right of any page on the Juniper Networks TechLibrary site, and do one of the following:
  • Click the thumbs-up icon [thumbs-up] if the information on the page was helpful to you.
  • Click the thumbs-down icon [thumbs-down] if the information on the page was not helpful to you or if you have suggestions for improvement, and use the pop-up form to provide feedback.
• E-mail—Send your comments to techpubs-comments@juniper.net. Include the document or topic name, URL or page number, and software version (if applicable).

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or Partner Support Service support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.

• JTAC policies—For a complete understanding of JTAC procedures and policies, review the JTAC User Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
• Product warranties—For product warranty information, visit http://www.juniper.net/support/warranty/.
• JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:

• Find CSC offerings: https://www.juniper.net/customers/support/
• Search for known bugs: https://prsearch.juniper.net/
• Find product documentation: https://www.juniper.net/documentation/
• Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/
• Download the latest versions of software and review release notes: https://www.juniper.net/customers/csc/software/
• Search technical bulletins for relevant hardware and software notifications: https://kb.juniper.net/InfoCenter/
• Join and participate in the Juniper Networks Community Forum: https://www.juniper.net/company/communities/
• Create a service request online: https://myjuniper.juniper.net

To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/

Creating a Service Request with JTAC

You can create a service request with JTAC on the Web or by telephone.

• Visit https://myjuniper.juniper.net.
• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see https://support.juniper.net/support/requesting-support/.

Revision History

February 2021—for the JSA Release 7.3.3 Fix Pack 7 (Patch 7) SFS

Copyright © 2021 Juniper Networks, Inc. All rights reserved.

Legal and Trademark Information

Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. and/or its affiliates in the United States and other countries. All other trademarks may be property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.