IBM Support

Release of QRadar Incident Forensics V7.4.0 SFS (740_QRadar_patchupdate-7.3.3.20200304205308)

Release Notes


Abstract

This technical note contains installation instructions, a list of new features, and resolved issues for the IBM Security QRadar Incident Forensics V7.4.0 (740_QRadar_patchupdate-7.3.3.20200304205308) SFS. These instructions are intended for administrators who are upgrading from QRadar Incident Forensics V7.3.1, V7.3.2 (except V7.3.2 Fix Pack 8) or V7.3.3 (Fix Pack 2 or earlier) to QRadar V7.4.0 by using an SFS file. Use this Fix Pack to upgrade all of your QRadar components.

Content

Known Issues

Known issues in QRadar Incident Forensics 7.4.0
Product Component Number Description
QRADAR EVENTS IJ23194 EVENT COLLECTION CAN STOP ON EVENT COLLECTORS DUE TO INCORRECT PIPELINEDISKMONITOR FREE SPACE CALCULATION

Resolved Issues

For a list of APAR links of resolved issues in QRadar Incident Forensics V7.4.0, see Authorized Program Analysis Reports .

Some APAR links might take 24 hours to display properly after a software release is posted to IBM Fix Central.

Resolved issues in QRadar Incident Forensics 7.4.0
Product Component Number Description
QRADAR SECURITY BULLETIN CVE-2020-4274 IBM QRadar SIEM is vulenrable to Authorization bypass
QRADAR SECURITY BULLETIN CVE-2020-4272 IBM QRadar SIEM is vulnerable to instantiation of arbitrary objects
QRADAR SECURITY BULLETIN CVE-2020-4271 IBM QRadar SIEM is vulnerable to PHP object injection
QRADAR SECURITY BULLETIN CVE-2020-4270 IBM QRadar SIEM is vulnerable to privilege escalation
QRADAR SECURITY BULLETIN CVE-2020-4294 IBM QRadar SIEM is vulnerable to Server-Side Request Forgery (SSRF)
QRADAR SECURITY BULLETIN CVE-2020-4269 IBM QRadar SIEM contains hard-coded credentials
QRADAR SECURITY BULLETIN CVE-2020-4272 IBM QRadar SIEM is vulnerable to instantiation of arbitrary objects
QRADAR SECURITY BULLETIN CVE-2020-4151 IBM QRadar SIEM is vulnerable to improper input validation
QRADAR SECURITY BULLETIN CVE-2019-2989 Multiple vulnerabilities in IBM Java SDK and IBM Java Runtime affect IBM QRadar SIEM
QRADAR SECURITY BULLETIN CVE-2019-4654 IBM QRadar SIEM is vulnerable to invalid certificate validation
QRADAR SECURITY BULLETIN CVE-2019-4593 IBM QRadar SIEM is vulnerable to information exposure
QRADAR SECURITY BULLETIN CVE-2019-4594 IBM QRadar SIEM is vulnerable to information exposure
QRADAR SECURITY BULLETIN CVE-2017-3164 IBM QRadar SIEM is vulnerable to Using Components with Known Vulnerabilities
QRADAR SECURITY BULLETIN CVE-2019-11135 IBM QRadar SIEM is vulnerable to side channel attack with Intel CPUs

Upgrade information

 

QRadar Incident Forensics V7.4.0 resolves reported issues from users and administrators from previous QRadar Incident Forensics versions. This cumulative software update fixes known software issues in your QRadar Incident Forensics deployment. QRadar Incident Forensics software updates are installed by using an SFS file, and updates all appliances attached to the QRadar Console.

The 740_QRadar_patchupdate-7.3.3.20200304205308 SFS file can upgrade QRadar Incident Forensics V7.3.1, V7.3.2 (except V7.3.2 Fix Pack 8) or V7.3.3 (Fix Pack 2 or earlier) to QRadar Incident Forensics V7.4.0. 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 Incident Forensics Installation Guide .

See QRadar: Software update check list for administrators for a list of steps to review before you update your QRadar Incident Forensics deployment.

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 QRadar Incident Forensics Administration Guide .
  • To avoid access errors in your log file, close all open QRadar Incident Forensics sessions.
  • The QRadar Incident Forensics software update 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, review the instructions in the QRadar Incident Forensics Installation Guide .

Installing the QRadar Incident Forensics V7.4.0 Software Update

These instructions guide you through the process of upgrading an existing QRadar Incident Forensics version at V7.3.1, V7.3.2 (except V7.3.2 Fix Pack 8) or V7.3.3 (Fix Pack 2 or earlier) to QRadar Incident Forensics V7.4.0.

Note: Installing the software update for the first time will require more time than previous releases. This is a result of architectural changes in QRadar V7.4.0.

Procedure
  1. Download the software update to install QRadar Incident Forensics V7.4.0 from the IBM Fix Central website: http://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+Incident+Forensics&release=All&platform=All&function=fixId&fixids=7.4.0-QRADAR-QIFSFS-2019.18.0.20200304205308&includeSupersedes=0&source=fc
  2. Use SSH to log in to your Console as the root user.
  3. To verify you have enough space (5GB) in /store/tmp for the QRadar 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 QRadar V7.4.0 versions /store/tmp is a symlink to the /storetmp partition.

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 5GB 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 that 5GB available.

Note: In QRadar V7.3.0 and later, an update to directory structure for STIG compliant directories reduces the size of several partitions. This can impact moving large files to QRadar.

  1. To create the /media/updates directory, type the following command:
      mkdir -p /media/updates
  2. Use SCP to copy the files to the QRadar Console to the /storetmp directory or a location with 5GB of disk space.
  3. Change to the directory where you copied the patch file. For example,
      cd /storetmp
  4. To mount the patch file to the /media/updates directory, type the following command:
      mount -o loop -t squashfs /storetmp/740_QRadar_patchupdate-7.3.3.20200304205308.sfs /media/updates
  5. To run the patch installer, type the following command:
      /media/updates/installer 

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

  6. Using the patch installer, select all.
    • The all option updates the software on all appliances in the following order:
      1. Console
      2. Remaining appliances.
    • If you do not select the all option, you must select your Console appliance.

      As of QRadar V7.2.6 Patch 4 and later, you 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 QRadar V7.2.6 Patch 4 to ensure that the Console appliance is always updated before managed hosts to prevent upgrade issues.

      If you want to patch systems in series, you 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.

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 you log 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 hosts 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, send an email to your team to inform them that they will need to clear their browser cache before they log in to the QRadar Incident Forensics interface.

Where do I find more information?


[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"Release Notes","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.4","Edition":"All Editions","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
28 January 2021

UID

ibm15737515