PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
OSP-OTHER-UNPRED SYSTEM TLS FAILS TLSV1.2 SERVER HELLO WITHO
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM RELEASE NUMBER MIN/MAX OPTION
---- -------- --------- ------- ------- ------
PRE 5770999 V7R3M0 MF67126 00/00 0000
CO 5770999 V7R3M0 MF67161 00/00 0000
CO 5770999 V7R3M0 MF67165 00/00 0000
CO 5770999 V7R3M0 MF67173 00/00 0000
NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels. This PTF may be a prerequisite
for future PTFs. By applying this PTF you authorize and agree to the
foregoing.
This PTF is subject to the terms of the 'IBM License Agreement for Machine
Code', the terms of which were provided in a printed document that was
delivered with the machine.
SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.
APAR Error Description / Circumvention
-----------------------------------------------
In response to a TLSv1.3 client hello, a TLSv1.2 server hello
that does not include the 2 bytes for the extension data length
fails with an Illegal Parameter alert for System TLS.
CORRECTION FOR APAR MA48442 :
-----------------------------
A TLSv1.2 server hello is not required to include the 2 byte
extension data length when the server has no extensions. System
TLS was updated to allow a TLSv1.2 server hello that does not
include the 2 byte extension data length.
CIRCUMVENTION FOR APAR MA48442 :
--------------------------------
None.
DESCRIPTION OF PROBLEM FIXED FOR APAR MA48453 :
-----------------------------------------------
System TLS handshake fails for SSLv2 client hello record for
some TLS protocol combinations.
CORRECTION FOR APAR MA48453 :
-----------------------------
System TLS was updated to handle SSLv2 client hello records for
valid TLS protocol combinations.
CIRCUMVENTION FOR APAR MA48453 :
--------------------------------
None.
Activation Instructions
None.
Special Instructions
None.
Default Instructions
THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
Supersedes
PTF/FIX NO(S). APAR TITLE LINE
-------------- ------------------------------------------------------------
MF67401 Heap Trap caused MSD due to DST referencing storage after so
MF67277 LIC-COMM-SSL System TLS OCSP stapling support
MF67163 LIC-COMM-SSL System TLS Curve25519 and Curve448 Support
MF60911 LIC-SSL TLS Record Loop
MF64534 LIC-SSL System TLS ROBOT attack VU#144389
MF64144 LIC-SSL SYSTEM TLS CLIENTHELLO DOES NOT INCLUDE EC_POINT_FOR
MF62915 LIC-SSL TLS Alert Record Leaked
MF60921 LIC-COMM-SSL VL2C00C630 *NETSECURE Audit
MF61141 LIC-SSL RSA Minimum Key Size Client Auth
Summary Information
System.............................. | i |
Models.............................. | |
Release............................. | V7R3M0 |
Licensed Program............... | 5770999 |
APAR Fixed.......................... | View details for APAR MA48442 View details for APAR MA48453 |
Superseded by:...................... | View fix details for PTF MF68374 |
Recompile........................... | N |
Library............................. | QSYS |
MRI Feature ........................ | NONE |
Cum Level........................... | C0310730 |
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.
Document Information
Modified date:
15 February 2021