Fix (APAR):  PH44271

Status:  Fix

Release:  9.0.5.10,9.0.5.9

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  PH44393 PH43122 PH43887 PH42030 PH41945 PH42862 PH40343 PH39660

CMVC Defect:  xxxxxx

Byte size of APAR:  53278751

Date: 2022-03-02

Abstract:  Vulnerability in IBM HTTP Server used by IBM WebSphere Application Server due to Expat (CVE-2022-25315 CVSS 7.8 and more)

Description/symptom of problem:  
PH44271 resolves the following problem:

ERROR DESCRIPTION:
Confidential for Security Integrity ifixCVE-2022-25235, CVE-2022-25236, CVE-2022-25313, CVE-2022-25315

PROBLEM SUMMARY:
Confidential for Security Integrity ifix CVE-2022-25235, CVE-2022-25236, CVE-2022-25313, CVE-2022-25315

PROBLEM CONCLUSION:
Confidential for Security Integrity ifix CVE-2022-25235, CVE-2022-25236, CVE-2022-25313, CVE-2022-25315


Directions to apply fix:  
Special Instructions: None

NOTE: The user must:
* Be at V1.8.5 or newer of the Installation Manager. Certain iFixes may require
  a newer version of the Installation Manager and the Installation Manager will
  inform you during the installation process if a newer version is required.
* Be logged in with the same authority level when unpacking a fix, fix pack, or
  refresh pack.

The IBM Information Center can provide details, if needed, on the use of the
Installation Manager to apply the interim fix:
http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.5/com.ibm.cic.agent.ui.doc/helpindex_imic.html.

1) Shutdown IBM HTTP Server
2) Apply the interim fix using Installation Manager
3) Restart IBM HTTP Server


Directions to remove fix:  
The IBM Information Center can provide details, if needed, on the use of the
Installation Manager to remove the interim fix:
http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.5/com.ibm.cic.agent.ui.doc/helpindex_imic.html.

1) Shutdown IBM HTTP Server
2) Remove the interim fix using Installation Manager
3) Restart IBM HTTP Server


Directions to re-apply fix:  
1) Stop IBM HTTP Server.
2) Follow the directions to apply the fix.
3) Restart IBM HTTP Server.


Additional Information: