Problem Note 50747: A client machine connects to a server machine even when the connection should not be allowed
 |  |  |  |  |
In UNIX operating environments, a client might be able to connect to a server even when the connection should not be allowed. This problem occurs when a Secure Sockets Layer (SSL) certificate uses a wildcard in the Common Name. The wildcard certificate verifies authenticity even when it should not be allowed to do so.
For example, suppose that a spawner is invoked with SSL encryption on a server named foobar.xyz.company-name.com. Then you have a client that uses an SSL certificate with a wildcard of *.AAA.company-name.com (rather than *.xyz.company-name.com) for the Common Name. In this situation, a connection between the client and server might be enabled even though it should not be allowed.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Base SAS | z/OS | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 |
| Z64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft® Windows® for x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows 8 Enterprise x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows 8 Pro 32-bit | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows 8 Pro x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.3_M2 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2003 Enterprise Edition | 9.3_M2 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2003 Standard Edition | 9.3_M2 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2003 for x64 | 9.3_M2 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2008 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows Server 2008 R2 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows Server 2008 for x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows Server 2012 Datacenter | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows Server 2012 Std | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Microsoft Windows XP Professional | 9.3_M2 | 9.3 TS1M2 | ||||
| Windows 7 Enterprise 32 bit | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows 7 Enterprise x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows 7 Home Premium 32 bit | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows 7 Home Premium x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows 7 Professional 32 bit | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows 7 Professional x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows 7 Ultimate 32 bit | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows 7 Ultimate x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Windows Vista | 9.3_M2 | 9.3 TS1M2 | ||||
| Windows Vista for x64 | 9.3_M2 | 9.3 TS1M2 | ||||
| 64-bit Enabled AIX | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| 64-bit Enabled HP-UX | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| 64-bit Enabled Solaris | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| HP-UX IPF | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Linux | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Linux for x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
| Solaris for x64 | 9.3_M2 | 9.4_M1 | 9.3 TS1M2 | 9.4 TS1M1 | ||
A fix for this issue for Base SAS 9.3_M2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/I22.html#50747A fix for this issue for SAS/Secure SSL 9.3_M2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/I22.html#50747| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2013-08-20 14:21:00 |
| Date Created: | 2013-08-15 12:04:31 |