Fix (APAR): PI90980 Status: Fix Release: 17.0.0.4,17.0.0.3 Operating System: AIX,HP-UX,IBM i,Linux,OS X,Solaris,Windows,iOS,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 2611074 Date: 2018-03-26 Abstract: POTENTIAL SPOOFING VULNERABILITY IN WEBSPHERE APPLICATION SERVER (CVE-2017-1788) Description/symptom of problem: PI90980 resolves the following problem: ERROR DESCRIPTION: POTENTIAL SPOOFING VULNERABILITY IN WEBSPHERE APPLICATION SERVER (CVE-2017-1788) LOCAL FIX: None PROBLEM SUMMARY: POTENTIAL SPOOFING VULNERABILITY IN WEBSPHERE APPLICATION SERVER (CVE-2017-1788) PROBLEM CONCLUSION: Code will be changes to correct this problem. Directions to apply fix: Fix applies to Editions: Release 17.0.0.3, 17.0.0.4 _x_ Application Server (Express or BASE) _x_ Network Deployment (ND) __ Edge Components _x_ Developer Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V1.4.3 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. The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before applying the iFixes. Restart WebSphere Application Server after applying the iFixes. Directions to remove fix: The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before removing the iFixes. Restart WebSphere Application Server after removing the iFixes. Directions to re-apply fix: 1) Shutdown WebSphere Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server. Additional Information: