IBM Support

Release of QRadar 7.4.2 Fix Pack 3 SFS (742_QRadar_FixPack3_2020.7.3.20210323172312)

Release Notes


This technical note contains installation instructions, and a list of new features and resolved issues for the IBM Security QRadar 7.4.2 Fix Pack 3 (742_QRadar_FixPack3_2020.7.3.20210323172312) SFS. These instructions are intended for administrators who are upgrading to QRadar 7.4.2 Fix Pack 3 by using an SFS file.


  • Auto update server changes

    To avoid interruptions with your software updates, you must change your auto update server configuration before 30 November 2020. A benign error message might be displayed when you update your configuration. For more information, see QRadar: Auto update server changes required before 30 Nov 2020 and IJ29298.

  • Deprecation of Active Directory authentication modules

    If you use a Kerberos-based Active Directory (AD) authentication you must move to the Lightweight Directory Access Protocol (LDAP) to authenticate to QRadar. The underlying open source component of the Kerberos-based Active Directory (AD) is being removed because the component library is no longer supported. When you attempt to upgrade QRadar software, a new error message stops the installation when Active Directory authentication configurations are detected. For more information, see Active Directory authentication modules deprecated from QRadar Console appliances.

  • Adobe Flash end of life and changes to Configuration Source Management (CSM)

    If you have a QRadar Risk Manager (QRM) appliance in your deployment, there are changes in Configuration Source Manager due to the impending end of life of Adobe Flash. For more information, see QRadar Risk Manager: Adobe Flash end of life and changes to Configuration Source Management (CSM).

Known issues in QRadar 7.4.2 Fix Pack 3

Error when readding a managed host after installing QRadar 7.4.2 Fix Pack 3
After you install QRadar 7.4.2 Fix Pack 3 and readd a managed host, you might receive an error. If you attempt to readd the managed host a second time, the managed host is added successfully. For more information, see IJ32056.

Resolved issues

The UBA app did not load properly in QRadar 7.4.2
QRadar 7.4.2 Fix Pack 3 resolves the issue where the User Behavior Analytics (UBA) app did not load properly for some users after an upgrade to QRadar 7.4.2 if you had UBA 3.7 or earlier. For more information, see IJ29455.

For a list of APAR links of resolved issues in QRadar 7.4.2 Fix Pack 3, 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.

Issues resolved in QRadar 7.4.2 Fix Pack 3
Product Component Number Description

Multiple vulnerabilities in IBM Java SDK and IBM Java Runtime affect IBM QRadar SIEM


Sudo as used by IBM QRadar SIEM is vulnerable to arbitrary code execution


Apache Tomcat as used by IBM QRadar SIEM is vulnerable to information disclosure


IBM QRadar SIEM is vulnerable to using components with known vulnerabilities


IBM QRadar SIEM is vulnerable to insecure inter-deployment communication


IBM QRadar SIEM is vulnerable to path traversal


IBM QRadar SIEM is vulnerable to Cross Site Scripting (XSS)


IBM QRadar SIEM is vulnerable to Cross domain information disclosure


IBM QRadar SIEM contains hard-coded credentials


IBM QRadar SIEM is vulnerable to Cross Site Scripting (XSS)


IBM QRadar SIEM may be vulnerable to a XML External Entity Injection attack (XXE)

Upgrade information


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

The 742_QRadar_FixPack3_2020.7.3.20210323172312 SFS file can upgrade the following QRadar versions to QRadar 7.4.2 Fix Pack 3:

  • QRadar 7.3.2 (Fix Pack 3 - Fix Pack 7) 
  • QRadar 7.3.3 (GA - Fix Pack 7) 
  • QRadar 7.4.0 (GA - Fix Pack 4) 
  • QRadar 7.4.1 (GA - Fix Pack 2)
  • QRadar 7.4.2 (GA - Fix Pack 2)
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.

See QRadar: Software update check list for administrators for a list of steps to review before you update your QRadar 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 Administration Guide.
  • To avoid access errors in your log file, close all open QRadar sessions.
  • The QRadar 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 Installation Guide.

Installing the QRadar 7.4.2 Fix Pack 3 Software Update

These instructions guide you through the process of upgrading to QRadar 7.4.2 Fix Pack 3

To update appliances in parallel, see: QRadar: How to Update Appliances in Parallel.
  1. Download the software update to install QRadar 7.4.2 Fix Pack 3 from the IBM Fix Central website:

    IMPORTANT: QRadar Incident Forensics uses a unique SFS file to upgrade to 7.4.3. See the Fix Central page for QRadar Incident Forensics to download the correct file.

  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 7.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 7.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/742_QRadar_FixPack3_2020.7.3.20210323172312.sfs /media/updates
  5. To run the patch installer, type the following command:

    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. No order required for remaining appliances. All remaining appliances can be updated in any order that you require.
    • If you do not select the all option, you must select your Console appliance.

      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.
  4. To ensure that all services are running, on the Admin tab, click Advanced > Deploy Full Configuration.


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 SIEM interface.

[{"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:
20 May 2021