Release Notes
Abstract
This technical note contains installation instructions, and a list of new features and resolved issues for the IBM Security QRadar 7.3.1 Patch 3 (7.3.1.20180327211425) SFS. These instructions are intended for administrators who use an SFS file to upgrade from QRadar 7.3.1 to QRadar 7.3.1 Patch 3.
Content
Upgrade information
QRadar 7.3.1 Patch 3 resolves 39 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. The software update can update all appliances attached to the QRadar Console. If you have installed any of the following QRadar versions, install software update 7.3.1-QRADAR-QRSIEM-20180327211425 to upgrade to QRadar 7.3.1 Patch 3:
| Current QRadar Version | Upgrades to QRadar 7.3.1 Patch 3? |
| QRadar 7.2.8 (any patch version) | No, see QRadar 7.3.1 Patch 3 ISO Release Notes. |
| QRadar 7.3.0 (any patch version) | Yes. Administrators can apply this SFS file to update to 7.3.1 Patch 3. |
| QRadar 7.3.1 | Yes. Administrators can apply this SFS file to update to 7.3.1 Patch 3. |
The 7.3.1-QRADAR-QRSIEM-20180327211425 SFS file can upgrade QRadar 7.3.0 to QRadar 7.3.1 Patch 3. However, this document does not cover all 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 QRadar Administration Guide.
- To avoid access errors in your log file, close all open QRadar sessions.
- The software update 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, review the instructions in the QRadar Installation Guide.
Installing the QRadar 7.3.1 Patch 3 Software Update
These instructions guide you through the process of upgrading an existing QRadar version from 7.3.1 to QRadar 7.3.1 Patch 3. For information about updating appliances in parallel, see: QRadar: How to Update Appliances in Parallel.
Procedure
- Download the software update to install QRadar 7.3.1 Patch 3 from the IBM Fix Central website: ibm.biz/BdZvhh
- Use SSH to log in to your Console as the root user.
- To verify that you have enough space (3 GB) in /storetmp 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.0 versions /storetmp is a symlink to the /storetmp partition. - 2nd best directory option: /tmp
This directory is available on all appliances, but in the 7.3.0 versions it is significantly smaller. Moving a file to this directory 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, and 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 3 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 that 3 GB 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.
- To create the /media/updates directory, type the following command: mkdir -p /media/updates
- Use SCP to copy the files to the /storetmp directory on the QRadar Console or a location with 3 GB of disk space.
- Change to the directory where you copied the software update file. For example, cd /storetmp
- To mount the software update file to the /media/updates directory, type the following command:
mount -o loop -t squashfs /storetmp/731_QRadar_patchupdate-7.3.1.20180202182152.sfs /media/updates - To run the software update 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 installation menu displays. - Using the software update 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 you require.
- 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 updated first. After the Console is updated, 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 update systems in series, you can update the Console first, then copy the software update to all other appliances and run the installer individually on each managed host. The Console must be updated 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 re-run the installer, the software update installation resumes.
- After the update completes and you have exited the installer, type the following command: umount /media/updates
- Clear your browser cache before logging in to the Console.
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, you can send an email to your team to inform them that they will need to clear their browser cache before logging in to the QRadar SIEM interface.
Known and Resolved Issues
Some APAR links in the following table might take 24 hours to display properly after a software release is posted to IBM Fix Central.
| Product | Component | Number | Description |
|---|---|---|---|
| QRADAR INCIDENT FORENSICS | SECURITY BULLETIN | CVE-2018-1418 | IBM QRadar Incident Forensics, as found in IBM QRadar SIEM, is vulnerable to an authentication bypass leading to remote command injection |
| QRADAR | SECURITY BULLETIN | CVE-2017-1724 | IBM QRadar SIEM is vulnerable to cross-site scripting |
| QRADAR INCIDENT FORENSICS | SECURITY BULLETIN | CVE-2017-1723 | IBM QRadar Incident Forensics, as used in IBM QRadar SIEM, is vulnerable to authenticated path traversal |
| QRADAR | SECURITY BULLETIN | CVE-2017-1722 | IBM QRadar SIEM is vulnerable to SQL Injection |
| QRADAR INCIDENT FORENSICS | SECURITY BULLETIN | CVE-2017-1721 | IBM QRadar Incident Forensics, as found in IBM QRadar SIEM, is vulnerable to remote code execution |
| QRADAR | SECURITY BULLETIN | CVE-2014-3576 | IBM QRadar SIEM contains vulnerable components and libraries |
| QRADAR | SECURITY BULLETIN | CVE-2011-4314 | IBM QRadar SIEM contains vulnerable components and libraries |
| QRADAR | SECURITY BULLETIN | CVE-2016-4970 | IBM QRadar SIEM contains vulnerable components and libraries |
| QRADAR | SECURITY BULLETIN | CVE-2015-5262 | IBM QRadar SIEM contains vulnerable components and libraries |
| QRADAR | SECURITY BULLETIN | CVE-2016-3092 | QRadar SIEM contains vulnerable components |
| QRADAR | SECURITY BULLETIN | CVE-2015-0250 | IBM QRadar SIEM contains vulnerable components |
| QRADAR | SECURITY BULLETIN | CVE-2016-9878 | IBM QRadar SIEM contains vulnerable components and libraries |
| QRADAR | SECURITY BULLETIN | CVE-2015-5262 | IBM QRadar SIEM contains vulnerable components and libraries |
| QRADAR | SECURITY BULLETIN | CVE-2017-1624 | IBM QRadar SIEM is vulnerable to incorrect permission assignment. |
| QRADAR | SECURITY BULLETIN | CVE-2017-1733 | IBM QRadar SIEM is vulnerable to information exposure through log files. |
| QRADAR | SECURITY BULLETIN | CVE-2017-12163 | Open Source Samba as used in IBM QRadar SIEM is vulnerable to information exposure. |
| QRADAR | SECURITY BULLETIN | CVE-2017-12629 | Open Source Apache Solr as used in IBM QRadar Incident Forensics is vulnerable to arbitrary code execution. |
| QRADAR | SEARCH | IJ00857 | RESOURCE LEAK IN ARIEL CAN CAUSE QUERY PROCESSING TO STOP |
| QRADAR | REPORTS | IV98739 | CHANGES MADE TO CUSTOM COLUMN DEFINITION LAYOUT IN LOG/FLOW ACTIVITY DO NOT PERSIST |
| QRADAR | SEARCH | IV95449 | USING THE 'UPDATE' BUTTON ON A LOG ACTIVITY SEARCH PAGE THE DAY OF A DST (TIME) CHANGE MOVES THE START/END TIME ONE HOUR |
| QRADAR | SEARCH | IV91635 | QUICK SEARCHES CANNOT BE REMOVED FROM THE QUICK SEARCH LIST |
| QRADAR | REPORTS | IJ01012 | A REPORT RUN AGAINST A LOG ACTIVITY SAVED AQL SEARCH MAY BE GENERATED WITH AN ERROR. |
| QRADAR | REPORTS | IJ00416 | LOG AND NETWORK ACTIVITY EXPORTS TO CSV DISPLAY INCORRECT COLUMN NAMES |
| QRADAR | REPORTS | IJ00066 | TABLE REPORTS USING ACCUMULATED AQL DATA DISPLAY INCORRECT COLUMNS |
| QRADAR | EVENT DATA | IJ03379 | EVENT DATA PROCESSED INTO SPILLOVER CAN SOMETIMES FAIL TO PARSE WHEN PROCESSED BY THE REGULAR QRADAR PIPELINE |
| QRADAR | API SEARCH | IV98260 | API SEARCHES USING A COMPLETED ARIEL SEARCH CAN SOMETIMES RETURN WITH AN ERROR 500 |
| QRADAR | REPORTS | IJ03534 | SOME GLOBAL VIEWS NOT WORKING AS EXPECTED AFTER UPGRADING TO 7.3.1.X CAUSING NO DATA IN DASHBOARDS AND FAILED REPORTS |
| QRADAR | KERNEL | IJ00141 | DISK MAINTENANCE DELETES /STORE/ARIEL/FLOWS (RECORDS AND PAYLOADS) DIRECTORY ON DATANODES THAT RECEIVE EVENTS ONLY |
| QRADAR NETWORK INSIGHTS | FLOW COLLECTION | IJ04056 | PORT BASED APPLICATION MAPPINGS ARE IGNORED WHEN USING QRADAR NETWORK INSIGHTS |
| QRADAR NETWORK INSIGHTS | FORENSICS | IJ00952 | QNI DECAPPER STOPPED BECAUSE OF A RHEL OUT OF MEMORY FUNCTION |
| QRADAR | HIGH AVAILABILITY | IJ03342 | NETFLOW TRAFFIC CONTAINING SUPERFLOWS CAN SOMETIMES REPORT INCORRECT FIRST/LAST PACKET TIME |
| QRADAR | APPLICATION INSTALL | IJ02076 | QRADAR APPS INSTALLED ON AN APPNODE CAN SOMETIMES FAIL TO LOAD/OPEN/INSTALL |
| QRADAR | APPLICATION INSTALL | IJ01144 | APPS THAT TAKE LONGER THAN 8 MINUTES TO INSTALL MAY BE STOPPED BY THE MARATHON HEALTH CHECK REGARDLESS OF THE APP HEALTH CHECK |
| QRADAR | APPLICATION INSTALL | IJ00207 | QRADAR APPLICATIONS CAN FAIL TO INSTALL OR UPGRADE WHEN THERE IS INSUFFICIENT FREE SPACE IN /TMP |
| QRADAR | USER INTERFACE | IV99511 | LOG SOURCE GROUP WINDOW CAN SOMETIMES FAIL TO LOAD WHEN GREATER THAN 1000 LOG SOURCES EXIST IN A GROUP |
| QRADAR | INSTALL/UPGRADE | IJ03213 | QRADAR SYSTEMS BUILT AT 7.2.2.-7.4 CAN FAIL TO UPGRADE TO 7.3.1.X WITH A 'TA_DSM_INFO' VIOLATES FOREIGN KEY ERROR |
| QRADAR | DSM EDITOR | IJ00975 | A SESSION LEAK IN TOMCAT MAY OCCUR WHEN USING THE DSM EDITOR |
| QRADAR | HIGH AVAILABILITY | IV94966 | XX48 HIGH AVAILABILITY APPLIANCES CAN BECOME UNRESPONSIVE DURING DRBD SYNCRONIZATION WHEN CONFIGURED WITH CROSSOVER |
| QRADAR | HIGH AVAILABILITY | IJ03669 | UPGRADE TO QRADAR 7.3.X CAN FAIL ON HIGH AVAILABILITY (HA) SYSTEMS WITH 'ERROR EXECUTING 30-CHECKPARTITIONS.SH' |
| QRADAR | INSTALL/UPGRADE | IJ03410 | QRADAR PATCH PRETEST CAN FAIL WHEN A DEPLOYMENT HAS MORE THAN NINE (9) NAT IDS |
| QRADAR | INSTALL/UPGRADE | IJ02095 | VIS CAN FAIL TO START DURING UPGRADE TO QRADAR 7.3.0.X |
| QRADAR | INSTALL/UPGRADE | IJ01522 | QRADAR UPGRADE FROM 7.2.8.X TO 7.3.0.X CAN SOMETIMES FAIL ON APPLIANCES WITH BONDED INTERFACES |
| QRADAR | INSTALL/UPGRADE | IJ01120 | FACTORY REINSTALL FAILS ON QRADAR APPLIANCES THAT HAVE BEEN UPGRADED FROM 7.2.8 TO 7.3.0 |
| QRADAR | INSTALL/UPGRADE | IJ00999 | UPGRADING TO QRADAR 7.3.0 MAY LEAD TO A 4GB ISO AND OTHER FILES IN /STORETMP |
| QRADAR | INSTALL/UPGRADE | IJ00902 | STATIC ROUTES CONFIGURED IN QRADAR 7.2.8 ARE REMOVED DURING AN UPGRADE TO 7.3.0 |
| QRADAR | INSTALL/UPGRADE | IJ00882 | AFTER A 7.3.0 UPGRADE, SERVICES MAY FAIL TO START ON THE APPLIANCE AFTER A REBOOT |
| QRADAR | LICENSING | IV99772 | 'THE NUMBER OF CONFIGURED LOG SOURCES IS APPROACHING OR HAS REACHED THE LICENSE LIMIT' SYSTEM EVENTS |
| QRADAR | LICENSING | IV97442 | 'THE EPS OR FPM LICENSE POOL IS OVER-ALLOCATED. PLEASE CONTACT YOUR ADMINISTRATOR' MESSAGE ON LOG/NETWORK ACTIVITY TAB |
| QRADAR | USER INTERFACE | IJ01488 | QRADAR'S TOMCAT PROCESS CAN RUN OUT OF AVAILABLE FILE HANDLES CAUSING USER INTERFACE STABILITY/FUNCTIONALITY ISSUES |
| QRADAR | DATABASE | IV85442 | THE X-FORCE SCASERVER PROCESS CAN FAIL TO START DUE TO DATABASE FILE CORRUPTION AFTER AN UPDATE |
| QRADAR VULNERABILITY MANAGER | SCAN POLICY | IV98247 | CLICKING 'SAVE' AFTER EDITING A SCAN POLICY CAN APPEAR TO HANG AND NOT SAVE SUCCESSFULLY |
| QRADAR VULNERABILITY MANAGER | REPORTS | IV95105 | REPORTS CREATED FROM VULNERABILITY SCAN PROFILES CAN SOMETIMES BE BLANK |
| QRADAR VULNERABILITY MANAGER | INSTALL/UPGRADE | IJ04398 | PATCH/UPGRADE TO QRADAR 7.3.1 PATCH 2 CAN HANG FOR AN EXTENDED PERIOD OF TIME (HOURS) WITH "VULN_MAP_ASSET_MV DOES NOT EXIST" |
| QRADAR VULNERABILITY MANAGER | SCAN PROFILE | IJ00368 | SAVING A SCAN PROFILE CAN TAKE LONGER THAN EXPECTED |
| QRADAR | API | IV98655 | REFERENCE SETS THAT CONTAIN LARGE DATASETS THAT ARE LOADED VIA THE API CAN SOMETIMES CAUSE UI INSTABILITY/INACCESSABILITY |
| QRADAR | USER INTERFACE | IV98452 | EMAIL RESPONSE USING CUSTOM EMAIL TEMPLATE DISPLAYS A TEMPLATE STRING CODE INSTEAD OF 'N/A' FOR NULL CUSTOM PROPERTIES |
| QRADAR | CUSTOM EVENT PROPERTIES | IJ02479 | CUSTOM EVENT PROPERTIES ASSIGNED TO A LOG SOURCE ARE NOT VISIBLE IN SEARCH FILTER FOR NON-ADMIN USER |
Where do I find more information?
[{"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.1","Edition":"All Editions","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27050917