| L8X075 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 69854 | SAS® 9.4M8 (TS1M8) installations fail on Microsoft Windows 11, and Windows Server 2022 Datacenter and Standard; and starting SAS® produces an error |
L8X001 |
| 69871 | MXG code cannot read TYPE 70/72 records that are longer than 32K record due to a change that IBM made |
L8X005 |
| 69974 * | Base SAS® does not correctly detect a Linux distribution on start-up and returns an "Unrecognized Linux Distribution" note |
L8X011 |
| 70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 |
L8X038 |
| 71105 | Tracebacks in the SAS log are displayed in plain text when runtime exceptions occur |
L8X075 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
NOTE: If you install this hot fix, you must also install hot fix L8Y022 for SAS Threaded Kernel Core Routines 9.4_M8.
If you install this hot fix to address the issue described in SAS Note 70340, you must also apply Base SAS 9.4_M8 hot fixes L8X082, and L8X086. |
|
|
| L8X078 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 70140 | The ODS PDF destination with ACCESSIBLE option and the PROC FACTOR procedure might generate a segmentation violation error |
L8X019 |
| 70305 | Using the PDFSECURITY=HIGH system option results in PDF output that is encoded with 128-bit RC4 encoding instead of AES 256 encoding |
L8X025 |
| 70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® |
L8X044 |
| 70805 | Some data points are plotted incorrectly in ODS Graphics output if there is a break in the Y axis |
L8X056 |
| 70827 | Text might be truncated when using the Column_Span option in the ODS Region statement |
L8X058 |
| 70831 | Using PROC MIXED with the ODS PDF destination, ENCODING=WHEBREW, and LOCALE=HEBREW_ISRAEL causes SAS® software to terminate |
L8X061 |
| 71167 | Encrypted PDF files might not require a password on Apple devices |
L8X077 |
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709.
To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). |
|
|
| L8X079 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 69920 | Attempting to clone a Git repository fails with "ERROR: Unable to load libgit2.module" |
L8X007 |
| 69932 | Attempting to clone a Git repository with the ed25519 keygen algorithm fails with "ERROR: Failed to authenticate with the remote repo" |
L8X007 |
| KB0040694 | Attempting to clone a Git repository fails with "ERROR: libgit2.so not found" with RHEL9 and OpenSSL 3.0.7 |
L8X079 |
NOTE: This hot fix requires additional manual updates. See SAS Note 69920 for details.
NOTE: If you install this hot fix and have SAS Studio 3.82 installed, you must also install hot fix M3T014. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| L8X082 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 69952 | Using the * comment operator mid-line within a format definition in PROC FORMAT might cause subsequent procedures steps to abend |
L8X006 |
| 69899 | Calling a user-defined function with the PROC FORMAT OTHER= argument can cause SAS® to stop responding |
L8X008 |
| 70504 * | Support for the IBM "System SSL" for z64 |
L8X030 |
| 70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 |
L8X035 |
| 70431 | The UNIVARIATE procedure might generate a Segmentation Violation Error in SAS |
L8X035 |
| 70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® |
L8X046 |
| 70869 | A security vulnerability exists when IOM TRACE logging is enabled |
L8X060 |
| KB0041113 | The FILENAME statement: SFTP access method might allow a remote code execution |
L8X082 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
NOTE: If you install this hot fix to address the issue described in SAS Note 70402, you must also apply L8X091 and M4B017 for Base SAS 9.4_M8.
If you install this hot fix to address the issue described in SAS Note 70340, you must also apply Base SAS 9.4_M8 hot fixes L8X086, L8X075 (Unix and Windows only), L8X091(MVS only)
If you install this hot fix you must also apply L8X047 for Base SAS 9.4_M8 and N3S001 for Base SAS User Interface 9.4 - M8
If you install this hot fix to address the issue described in SAS Note 70869, you must also apply M4B017 for Base SAS 9.4_M8.
All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709.
To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). |
|
|
| L8X083 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® |
L8X045 |
| KB0041033 | The message "FATAL: Unrecoverable I/O error detected in the execution of the DATA step program..." occurs when transcoding a zoned decimal variable |
L8X083 |
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709.
To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). |
|
|
| L8X086 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 |
L8X037 |
| 70797 | Running SAS® 9.4M7 (TS1M7) or SAS® 9.4M8 (TS1M8) with non-English European languages might result in an error |
L8X053 |
| NOTE: If you install this hot fix to address the issue described in SAS Note 70340, you must also apply Base SAS 9.4_M8 hot fixes L8X082, L8X075 (Unix and Windows only), L8X091(MVS only) |
|
|
| L8X091 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 70197 | Initialization of SAS® 9.4M5 (TS1M5) and later for z/OS fails with a system abend 0C4-10 when the machine is configured for more than 16 processors |
L8X023 |
| 70504 * | Support for the IBM "System SSL" for z64 |
L8X029 |
| 70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 |
L8X039 |
| 70796 | You encounter the message, "ERROR 23-2: Invalid option name PERMISSION" in SAS® 9.4M7 (TS1M7) |
L8X054 |
| 70771 | SAS/ACCESS ® Interface to DB2 threads are left active when used from the SAS/CONNECT® server and the SAS/CONNECT server abruptly terminates |
L8X063 |
| 66729 | The CONTENTS procedure on z/OS with the V6 LIBNAME engine generates incorrect times for the "Created" and "Last Modified" time values |
L8X068 |
| 70978 | Pervasive Encryption fails with an error similar to "ERROR 22-7: Invalid option name..." |
L8X069 |
| 71105 | Tracebacks in the SAS log are displayed in plain text when runtime exceptions occur |
L8X076 |
| KB0042824 | Using EMAILSYS=CSSMTP might result in "ERROR: Invalid option name BYCAPSOT" in SAS® 9.4M8 on z/OS |
L8X088 |
| KB0041766 | TLS Server Name Indication (SNI) support is not available in SAS® 9.4M8 (TS1M8) and SAS® 9.4M9 (TS1M9) on z/OS |
L8X091 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
NOTE: If you install this hot fix, you must also install hot fix L8Y022 for SAS Threaded Kernel Core Routines 9.4_M8.
If you install this hot fix to address the issue described in SAS Note 70402, you must also apply L8X082 and M4B017 for Base SAS 9.4_M8.
If you install this hot fix to address the issue described in SAS Note 70340, you must also apply Base SAS 9.4_M8 hot fixes L8X082, and L8X086. |
|
|
| L8X095 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 70088 | Passwords appear in the SAS® log when the SQL procedure contains the _tree option and an embedded LIBNAME statement |
L8X002 |
| 70090 | A "Parse Failure..." message occurs in the SAS® log when running SPD Server PROC SQL with hex literals |
L8X002 |
| 70279 | The SUBSTRN and KSUBSTRN functions used in PROC SQL with a numeric first argument return an incorrect result |
L8X032 |
| 70641 | The column alias is not used in an ON clause that is sent to a database in SAS/ACCESS® Interface to Vertica |
L8X043 |
| 70801 | The SQL procedure displays the note “The execution of this query involves performing one or more Cartesian product joins that can not be optimized” |
L8X049 |
| KB0043530 | The error "Provided buffer is not large enough" occurs in SAS/ACCESS® Interface to ODBC |
L8X089 |
| KB0043996 | Read performance improvements have been made to SAS/ACCESS® Interface to Google BigQuery |
L8X095 |
NOTE: If you install this hot fix, you must also install hot fix L8X096 for Base SAS 9.4_M8.
If you install this hot fix and have SAS/ACCESS Interface to Google BigQuery 9.43 installed, you must also install hot fix M7Z014. |
|
|
| L8X096 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| KB0043945 | The data step EXIST() function might return incorrect results when you test for views |
L8X092 |
| KB0043996 | Read performance improvements have been made to SAS/ACCESS® Interface to Google BigQuery |
L8X096 |
NOTE: If you install this hot fix, you must also install hot fix L8X095 for Base SAS 9.4_M8.
If you install this hot fix and have SAS/ACCESS Interface to Google BigQuery 9.43 installed, you must also install hot fix M7Z014. |
|
|
| M4B017 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 70230 | SAS® 9.4M8 (TS1M8) might display an OpenSSL 3 "legacy" provider warning at initialization |
M4B001 |
| 70859 | An intermittent exception occurs in SAS Workspace Server when a client is no longer running |
M4B002 |
| 70496 | The SAS® Environment Manager Service Architecture enablement might fail on getDBMirror if FIPS is enabled |
M4B004 |
| 70783 | SAS® Infrastructure for Risk Management job flows might fail due to an encryption failure |
M4B005 |
| 70869 | A security vulnerability exists when IOM TRACE logging is enabled |
M4B006 |
| 70846 | SAS® 9.4M8 (TS1M8) client connections to SAS® Cloud Analytic Services fail with the error "Missing CA trust list" |
M4B007 |
| 70905 | Support for the 2048 and 4096 key lengths with AES encryption on z/OS |
M4B008 |
| 71064 | Performance improvements with SAS/SECURE™ and AES encryption |
M4B010 |
| 71068 | SAS® 9.4M8 (TS1M8) encounters OpenSSL errors on RHEL 9.5 |
M4B010 |
| KB0041324 | The launch of the server (SASApp - Workspace Server) process failed with an unknown status code" error might occur with the SAS Workspace Server |
M4B012 |
| KB0041538 | Deprecation of the NETENCRYPTALGORITHM (NETENCRALG) system option values AES, DES, RC2, RC4, and TripleDES |
M4B013 |
| KB0042168 | Executing SAS code using TLS 1.3 fails with "ERROR: Encryption runtime execution error |
M4B013 |
| KB0042343 | Using PROC AUTHLIB with two kinds of quotation marks can cause SAS® Metadata Server to stop responding |
M4B014 |
| KB0042866 | SAS/CONNECT® SIGNON fails with "Network request failed ...." when using TLS 1.3 and OpenSSL 3 in RHEL 9 and later |
M4B015 |
| 70504 | Support for the IBM "System SSL" for z64 |
M4B017 |
| KB0041766 | TLS Server Name Indication (SNI) support is not available in SAS® 9.4M8 (TS1M8) and SAS® 9.4M9 (TS1M9) on z/OS |
M4B017 |
NOTE: If you install this hot fix to address the issue described in SAS Note 70402, you must also apply L8X091 and L8X082 for Base SAS 9.4_M8.
If you install this hot fix to address the issue described in SAS Note 70869, you must also apply L8X082 for Base SAS 9.4_M8.
If you install this hot fix to address the issue described in KB0041766, you must also install hot fix M3Y011. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| M8S003 |
| Base SAS 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| 70344 | The PHREG procedure contains a stack-corruption vulnerability if you incorrectly specify the RUN statement |
M8S001 |
| 70505 | PROC FCMP package names might not find the function and return "WARNING: Cannot find function 'function_name' in any of the libraries specified" |
M8S001 |
| 70466 | SAS® Model Implementation Platform returns an error when loading a large number of models |
M8S001 |
| 70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® |
M8S002 |
| KB0040884 | Passing a missing value for a pointer argument to a C function from an FCMP function does not work as expected |
M8S003 |
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709.
To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes