The applicable hot fix refreshes the trusted CA content used by the SAS Security Certificate Framework and rebuilds the SAS truststores to prevent trust of the affected certificate chains.
Potential Impact
An attacker who can use a forged certificate might impersonate a server or intercept TLS-protected traffic when a SAS process connects to a server that presents an affected certificate chain.
The certificate incident does not by itself indicate that a SAS system has been compromised, and SAS has reported no evidence of exploitation affecting SAS systems at the time of publication.
Select the Applicable Hot Fix
SAS 9.4M9 contains multiple SAS Security Certificate Framework builds. Install only the hot fix that matches the build in your deployment. The hot fix page and platform-specific documentation identify the supported build.
| SAS 9.4M9 Release Stream | Certificate Framework Version | Required Hot Fix |
|---|
| 25w25-based release | 9.49658 | S1M002 |
| 26w25-based release | 9.49660 | S1N002 |
| 26w38-based release | 9.49662 | S1P002 |
If you cannot determine which release stream or Certificate Framework version is installed, use the hot fix analysis process or contact SAS Technical Support before installing a package.
Solution
Apply the one hot fix that matches the SAS Security Certificate Framework build in each SAS 9.4M9 installation.
- Review the hot fix documentation. Use the platform-specific instructions on the Hot Fix Download page. Follow the prerequisites and outage guidance in that documentation before making changes.
- Protect local customizations. Record or back up customer-added trusted certificates according to your organization's change-management and recovery procedures.
- Install the applicable hot fix. Install the package on every machine in the SAS deployment where the applicable SAS Security Certificate Framework is installed.
- Restart and verify. Restart SAS applications and servers as directed by the hot fix documentation. Verify that the hot fix identifier is recorded in the SAS Deployment Registry and that the installation completed without errors.
- Review customer-added eMudhra certificates. The hot fix preserves customer-provided certificates when it rebuilds the SAS truststores. If your organization previously added an affected eMudhra certificate, remove it with SAS® Deployment Manager and add a clean replacement, if required.
If You Cannot Install the Hot Fix Immediately
Use the manual-remediation article in Related Information section to block the eight compromised intermediate certificates in the SAS Private JRE and remove the associated eMudhra roots from SAS truststores. Apply the hot fix as soon as your change window permits.
Verification
- Confirm that the expected hot fix identifier appears in the SAS Deployment Registry.
- Review the hot fix installer and post-installation logs and resolve any reported errors.
- If required by your security or audit process, run the certificate-remediation utility in dry-run mode and confirm that no matching SAS-delivered eMudhra root certificates remain.
Related Information