IBM Support

Release of the QRadar 7.3.1 Patch 4 SFS (7.3.1.20180507202600)

Release Notes


Abstract

A list of the installation instructions, new features, and includes resolved issues list for the release of IBM Security QRadar 7.3.1 Patch 4 (7.3.1.20180507202600) SFS. These instructions are intended for administrators upgrading from QRadar 7.3.0 or 7.3.1 to QRadar 7.3.1 Patch 4 using an SFS file.

Content


Important advisories in this update
This QRadar software update includes an operating system mitigation for the side-channel analysis vulnerability known as Spectre (Variant 1) and Meltdown (Variant 3). Due to a potential change to search performance in Meltdown (Variant 3), a new installation prompt is displayed to administrators so they can decide how the mitigation is applied. Installation of this update is not intended to, nor will it provide mitigation measures against Spectre Variant 2 (CVE-2017-5715). The mitigation for Variant 2/Spectre requires an OEM microcode/BIOS update on appliances. For information about other variants for Spectre and Meltdown, see the following IBM Flash Notice: http://www.ibm.com/support/docview.wss?uid=swg22012320.

This update contains a mitigation for CVE-2017-5754 Variant 3/Meltdown provided by Red Hat that can impact search performance. Administrators must read the release notes before they install this update.

Choices:

1) Enable: Turn ON the mitigation for Variant 3/Meltdown on all appliances.
2) Disable: Turn OFF the mitigation for Variant 3/Meltdown on all appliances. IF YOU CHOOSE NOT TO ENABLE THIS UPDATE TO ADDRESS CVE-2017-5754, YOU WILL NOT HAVE ANY PROTECTION AGAINST VARIANT 3/MELTDOWN.
3) Abort patch.


CVEID: CVE-2017-5753 (Variant 1/Spectre)
MITIGATION: Enabled by default during the installation of QRadar 7.3.1 Patch 4 and cannot be disabled.
DESCRIPTION: Intel Haswell Xeon, AMD PRO and ARM Cortex A57 CPUs could allow a local authenticated attacker to obtain sensitive information, caused by a bounds check bypass in the CPU speculative branch instruction execution feature. By conducting targeted cache side-channel attacks, an attacker could exploit this vulnerability to cross the syscall boundary and read data from the CPU virtual memory.
IMPACT: No performance impact.

CVEID: CVE-2017-5754 (Variant 3/Meltdown)
MITIGATION: An installation prompt is provided to enable or disable this mitigation on appliances. A utility is also provided to allow administrators to enable or disable the mitigation for CVE-2017-5754 (Variant 3/Meltdown) post-installation, see Installation wrap-up for further details. IBM cannot be held responsible for risks incurred by administrators who do not enable the mitigation of CVE-2017-5754 (Variant 3/Meltdown).
IF YOU CHOOSE NOT TO ENABLE THIS UPDATE TO ADDRESS CVE-2017-5754, YOU WILL NOT HAVE ANY PROTECTION AGAINST VARIANT 3/MELTDOWN.
DESCRIPTION: Intel Haswell Xeon, AMD PRO and ARM Cortex A57 CPUs could allow a local authenticated attacker to obtain sensitive information, caused by a rogue data cache load in the CPU speculative branch instruction execution feature. By conducting targeted cache side-channel attacks, an attacker could exploit this vulnerability to cause the CPU to read kernel memory from userspace before the permission check for accessing an address is performed.
IMPACT: Search performance degradation has been observed on appliances when the mitigation for Variant 3/Meltdown is enabled. Administrators who want to evaluate search duration on appliances before they apply the mitigation can review the following technical note: Search performance evaluation for CVE-2017-5754 (Variant 3/Meltdown).


Firmware notice
The mitigation for Variant 2/Spectre requires an OEM microcode/BIOS update on appliances. For more information on firmware releases, see: https://ibm.biz/qradarfirmware.


Performance assessment summary
Administrators can expect performance degradation after they enable the mitigation for the vulnerability.

  • A 3% to 6% increase in CPU utilization has been observed across all workloads on appliances after the mitigation applied.
  • Search performance for most common search types has been observed to degrade by 0% to 10%, with the following exceptions:
    • Searches that use indexed criteria and match a moderate number of results (less than 10% of the total searched dataset) are expected to be degraded between 3% to 20%.
    • Open-ended searches that have no limit applied to the query and return a very large number of results (30% of the total searched dataset or more) are expected to be degraded by up to 2x.
  • The impact on data processing is estimated to be in the 0% to 20% range.
  • High availability on 1 Gbit network is not affected. The initial high availability setup speed and catch-up replication speed after fail-over will be lower on 10 Gbit network. However, the replication rate is still in the multiple hundreds MB/s, which is sufficient for real time replication.


Upgrade information
Fix packs are cumulative software updates to fix known software issues in your QRadar deployment using an SFS file. The fix pack can update all appliances attached to the QRadar Console. If your deployment is installed with any of the following QRadar versions, you can install fix pack 7.3.1-QRADAR-QRSIEM-20180507202600 to upgrade to the latest QRadar 7.3.1 version.

Current QRadar VersionUpgrades to QRadar 7.3.1 Patch 4?
QRadar 7.2.8 (any patch version)See the QRadar 7.3.1 ISO release notes.
QRadar 7.3.0 (any patch version)Yes. the instructions in this release note can update the deployment to QRadar 7.3.1 Patch 4.
QRadar 7.3.1 (any patch version)Yes. the instructions in this release note can update the deployment to QRadar 7.3.1 Patch 4.


The 7.3.1-QRADAR-QRSIEM-20180507202600 SFS file can upgrade QRadar 7.3.0 to QRadar 7.3.1. However, this document does not cover all of the installation messages and requirements, such as changes to appliance memory requirements or browser requirements for QRadar. To review any additional requirements, see the QRadar Upgrade Guide.

Before you begin
Ensure that you take the following precautions:

  • Back up your data before you begin any software upgrade. For more information about backup and recovery, see the IBM Security QRadar Administration Guide.
  • To avoid access errors in your log file, close all open QRadar sessions.
  • The fix pack for QRadar 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 QRadar Installation Guide.


Installing the QRadar 7.3.1 Patch 4 Fix Pack
The instructions guide administrators through the process of upgrading an existing QRadar deployment to QRadar 7.3.1 Patch 4. If the administrator is interested in updating appliances in parallel, see: QRadar: How to Update Appliances in Parallel.


Procedure

  1. Download the update to install QRadar 7.3.1 Patch 4 from the IBM Fix Central website: http://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+SIEM&release=7.3.0&platform=All&function=fixId&fixids=7.3.1-QRADAR-QRSIEM-20180507202600&includeSupersedes=0&source=fc
  2. Using SSH, log in to your Console as the root user.
  3. To verify you have enough space (3GB) in /store/tmp for the QRadar Console, type:
    df -h /tmp /storetmp /store/transient | tee diskchecks.txt
    • Best directory option: /storetmp
      It is available on all appliance types, is not cleaned up if you need to postpone your update, and is available on all appliance types at all versions. In QRadar 7.3.1 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.1 versions 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 QRadar 7.2.1 and is allocated 10% of the overall /store directory. However, this directory does not exist on all appliances, such as QFlow or QRadar Network Insights and might not be an actual partition on all appliances.


      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 3GB of space available in a directory to copy the SFS before you attempt to move the file to a managed host. If required, free up disk space on any host that has less than 3GB available.


      Note:
      In QRadar 7.3.1 and later, an update to directory structure for STIG compliant directories reduces the size of several partitions. This directory structure change can impact administrators who attempt to move large files to QRadar appliances.

  4. To create the /media/updates directory, type the following command: mkdir -p /media/updates
  5. Using SCP, copy the files to the QRadar Console to the /storetmp directory or a location with 3GB of disk space.
  6. Change to the directory where you copied the patch file. For example, cd /store/tmp
  7. To mount the patch file to the /media/updates directory, type the following command:
    mount -o loop -t squashfs /storetmp/731_QRadar_patchupdate-7.3.1.20180507202600.sfs /media/updates
  8. To run the patch installer, type the following command: /media/updates/installer
    Note: The administrator might experience a short delay before the installation menu is displayed.
  9. Using the patch installer, select all.
    • The all option updates the software on all appliances in the following order:


      1. Console
      2. No order required for remaining appliances. All remaining appliances can be updated in any order .

    • If you do not select the all option, you must select your Console appliance.

      As of QRadar 7.2.6 Patch 4 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 is displayed in the installation menu. This change was made starting with QRadar 7.2.6 Patch 4 to ensure that the Console appliance is always updated before managed hosts to prevent upgrade issues.

      If administrators want to patch systems in parallel, they can update the Console first, then copy the patch to all other appliances and run the patch 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.

  10. Wait for the update to QRadar 7.3.1 Patch 4 complete. The appliance will reboot to complete the installation.

    Results
    A summary of the fix pack installation advises you of any managed host that failed to update. If the fix pack fails to update a managed host, you can copy the fix pack to the host and run the installation locally.

Installation wrap-up
  1. Due to the potential search performance change when CVE-2017-5754 (Variant 3/Meltdown) is enabled, the installation of QRadar 7.3.1 Patch 4 includes a utility to allow administrators to enable or disable the mitigation after the initial installation completes. Administrators must be aware of the security implications if they choose to use this utility to disable the mitigation for CVE-2017-5754 (Variant 3/Meltdown). IBM cannot be held responsible for risks incurred by administrators who choose to disable the mitigation for CVE-2017-5754.
    • To enable the mitigation on all hosts from the QRadar Console, type: /opt/qradar/bin/configure-spectre-meltdown-fixes.sh enable-all
    • To enable the mitigation on an individual appliance, SSH to the individual appliance and type: /opt/qradar/bin/configure-spectre-meltdown-fixes.sh enable 
    • To disable the mitigation on all hosts from the QRadar Console, type: /opt/qradar/bin/configure-spectre-meltdown-fixes.sh disable-all
    • To disable the mitigation on an individual appliance, SSH to the individual appliance and type: /opt/qradar/bin/configure-spectre-meltdown-fixes.sh disable 
  2. After all hosts are updated, advise your team that they must clear their browser cache before logging in to QRadar SIEM.
  3. To unmount the /media/cdrom directory on all hosts, type:
    /opt/qradar/support/all_servers.sh -C -k “umount /media/updates"
  4. Delete the SFS file from all appliances.

    Results
    The installation is complete. For more information about the security fixes in this release, see the resolved issues list.

Resolved issues in QRadar 7.3.1 Patch 4
Product Component Number Description
QRADARSECURITY BULLETINCVE-2017-5753, CVE-2017-5715, CVE-2017-5754IBM QRADAR SIEM HAS RELEASED 7.3.1 PATCH 4 IN RESPONSE TO THE VULNERABILITIES KNOWN AS SPECTRE AND MELTDOWN
QRADAREVENTSIJ02819'...SENT A TOTAL OF XXXX EVENT(S) DIRECTLY STORAGE...QUEUE IS AT 0 PERCENT CAPACITY" DURING OVER LICENSE EPS SPIKES
QRADAROFFENSESIJ00971AN APPLICATION ERROR MAY OCCUR IN THE OFFENSE TAB WHEN THE END TIME FOR AN OFFENSE IS IN THE FUTURE
QRADARSEARCHESIJ04906USING THE RIGHT-CLICK FILTER 'SOURCE OR DESTINATION IP IS...' IN A LOG ACTIVITY SEARCH DOES NOT WORK AS EXPECTED
QRADARSEARCHESIJ05806SOME LOG ACTIVITY SEARCHES STOP RETURNING RESULTS FROM LOG SOURCE GROUPS AFTER PATCH/UPGRADE TO QRADAR 7.3.1




Where do I find more information?



[{"Product":{"code":"SSBQAC","label":"IBM QRadar SIEM"},"Business Unit":{"code":"BU008","label":"Security"},"Component":"Release Notes","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.3.1","Edition":"All Editions"}]

Document Information

Modified date:
17 June 2018

UID

swg27050747