SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 70142: SAS® 9.4M7 (TS1M7) includes end-of-life Log4J version 1 libraries

DetailsHotfixAboutRate It

SAS 9.4M7 includes end-of-life Log4J version 1 libraries that might be flagged by security scanners. These libraries have been replaced with Reload4J in order to alleviate security concerns and scan findings for those who cannot upgrade to SAS® 9.4M8 (TS1M8). 

Refer to Log4j v1 Vulnerabilities and SAS Security Update for SAS® 9.4M7 (TS1M7) for details and instructions before applying hot fixes. 

Click the Hot Fix tab in this note to access the hot fix for this issue.

Additional Notes:

Log4j v1 filenames are preserved in the SASHome and SASConfig directories in order to eliminate the need for code changes in the SAS software. Deployment tools installed to the SASHome directory, such as SAS® Deployment Manager, use the Reload4j libraries with the preserved Log4j v1 filenames.

Because Log4 v1 filenames in your SASHome and SASConfig directories are preserved, security scanning utilities that evaluate the filenames might incorrectly identify the updated Reload4j libraries as Log4j v1 libraries. You should examine any Log4j v1 jar file that is identified by security scanning utilities to verify that the content of the jar file is Reload4j.

The SAS® 9.4M7 Deployment Wizard (SDW) and the SAS® Migration Utility (SMU) use Log4j v1 libraries that are in the SAS Software Depot directory for installations and migrations. The Log4j v1 libraries in that directory are not in use when SAS software is running. SAS® 9.4M8 (TS1M8) uses Log4J v2 libraries.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemBase SASz/OS9.4_M79.4 TS1M7
z/OS 64-bit9.4_M79.4 TS1M7
Microsoft® Windows® for x649.4_M79.4 TS1M7
Microsoft Windows 8 Enterprise 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8 Enterprise x649.4_M79.4 TS1M7
Microsoft Windows 8 Pro 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8 Pro x649.4_M79.4 TS1M7
Microsoft Windows 8.1 Enterprise 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8.1 Enterprise x649.4_M79.4 TS1M7
Microsoft Windows 8.1 Pro 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8.1 Pro x649.4_M79.4 TS1M7
Microsoft Windows 109.4_M79.4 TS1M7
Microsoft Windows 119.4_M79.4 TS1M7
Microsoft Windows Server 20089.4_M79.4 TS1M7
Microsoft Windows Server 2008 R29.4_M79.4 TS1M7
Microsoft Windows Server 2008 for x649.4_M79.4 TS1M7
Microsoft Windows Server 2012 Datacenter9.4_M79.4 TS1M7
Microsoft Windows Server 2012 R2 Datacenter9.4_M79.4 TS1M7
Microsoft Windows Server 2012 R2 Std9.4_M79.4 TS1M7
Microsoft Windows Server 2012 Std9.4_M79.4 TS1M7
Microsoft Windows Server 20169.4_M79.4 TS1M7
Microsoft Windows Server 20199.4_M79.4 TS1M7
Microsoft Windows Server 20229.4_M79.4 TS1M7
Windows 7 Enterprise 32 bit9.4_M79.4 TS1M7
Windows 7 Enterprise x649.4_M79.4 TS1M7
Windows 7 Home Premium 32 bit9.4_M79.4 TS1M7
Windows 7 Home Premium x649.4_M79.4 TS1M7
Windows 7 Professional 32 bit9.4_M79.4 TS1M7
Windows 7 Professional x649.4_M79.4 TS1M7
Windows 7 Ultimate 32 bit9.4_M79.4 TS1M7
Windows 7 Ultimate x649.4_M79.4 TS1M7
64-bit Enabled AIX9.4_M79.4 TS1M7
64-bit Enabled Solaris9.4_M79.4 TS1M7
HP-UX IPF9.4_M79.4 TS1M7
Linux for x649.4_M79.4 TS1M7
Solaris for x649.4_M79.4 TS1M7
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.