IBM Support

Release of QRadar 7.3.3 Fix Pack 9 SFS (7.3.3-QRADAR-QRSIEM-20210716155826)

Release Notes


This technical note contains installation instructions, a list of new features, and resolved issues for the IBM Security QRadar 7.3.3 Fix Pack 9 (7.3.3-QRADAR-QRSIEM-20210716155826) SFS. These instructions are intended for administrators who are upgrading to QRadar 7.3.3 Fix Pack 9 by using an SFS file.


More secure operating system

QRadar 7.3.3 Fix Pack 9 runs on Red Hat® Enterprise Linux® version 7.9. The upgrade to RHEL 7.9 is necessary to continue receiving security updates from Red Hat Enterprise Linux.

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.

Changes to Offenses API

The Offenses API is updated to include two new fields:
  • last_persisted_time - The number of milliseconds since epoch when an offense field was last updated.
  • first_persisted_time - The number of milliseconds since epoch at the time when the offense was created.

Resolved Issues

For a list of APAR links of resolved issues in QRadar 7.3.3 Fix Pack 9, 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.3.3 Fix Pack 9
Product Component Number Description

IBM QRadar SIEM is vulnerable to Using Components with Known Vulnerabilities


Apache PDFBox as used by IBM QRadar Incident Forensics is vulnerable to denial of service


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


IBM QRadar SIEM is vulnerable to an XML External Entity Injection (XXE) attack


IBM QRadar SIEM uses weaker than expected cryptographic algorithms


IBM QRadar SIEM is vulnerable to Using Components with Known Vulnerabilities


Change to search query syntax

As of QRadar 7.3.3 Fix Pack 2, the QRadar Incident Forensics search engine no longer supports spaces in field-specific searches. For example, the following queries are invalid:

  • Content: text
  • TcpPort: 80 AND IPAddress: ""
These queries are valid:
  • Content:text
  • TcpPort:80 AND IPAddress:""

Upgrade information


QRadar 7.3.3 Fix Pack 9 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 7.3.3-QRADAR-QRSIEM-20210716155826 SFS file can upgrade the following QRadar versions to QRadar 7.3.3 Fix Pack 9:

  • QRadar 7.3.0 (any version)
  • QRadar 7.3.1 (any version)
  • QRadar 7.3.2 (any version)
  • QRadar 7.3.3 (any version)

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.3.3 Fix Pack 9 Software Update

These instructions guide you through the process of upgrading to QRadar 7.3.3 Fix Pack 9. To update appliances in parallel, see: QRadar: How to Update Appliances in Parallel.

Important: You can use the verify signature tool to validate the integrity of your downloads from IBM Fix Central or Passport Advantage. For more information, see How to verify downloads from IBM Fix Central are trusted and code signed.

  1. Download the software update to install QRadar 7.3.3 Fix Pack 9 from the IBM Fix Central website:
  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.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 the version 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.

      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 or later, an update to directory structure for STIG compliant directories reduces the size of several partitions. This can impact moving large files to QRadar.

  4. To create the /media/updates directory, type the following command:
    mkdir -p /media/updates
  5. Use SCP to copy the files to the QRadar Console to the /storetmp directory or a location with 5GB of disk space.

    Important: If the SFS file is in the /storetmp directory and you do not upgrade, when the overnight utility runs, the SFS file is deleted. For more information, see Daily disk maintenance (
  6. Change to the directory where you copied the patch file. For example,
    cd /storetmp
  7. To mount the patch file to the /media/updates directory, type the following command:
    mount -o loop -t squashfs /storetmp/733_QRadar_FixPack9-2019.14.9.20210716155826.sfs /media/updates
  8. 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.

  9. Using the patch installer, select the patch option that you want to use.
    • 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 7.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 7.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.


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.

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

Document Information

Modified date:
01 March 2022