Citrix ADC security vulnerabilities

Citrix ADC security vulnerabilities

Citrix ADC security vulnerabilities description



A new security vulnerability with ID CVE-2021-22955 (Unauthenticated denial of service) has been discovered in Citrix ADC, which affects the following Citrix products and firmware versions:



- Citrix ADC and Citrix Gateway 13.0 before 13.0-83.27 

- Citrix ADC and Citrix Gateway 12.1 before 12.1-63.22 

- Citrix ADC and NetScaler Gateway 11.1 before 11.1-65.23 

- Citrix ADC 12.1-FIPS before 12.1-55.257 

Also a new security vulnerability with ID CVE-2021-22956 (Temporary disruption of the Management GUI, Nitro API and RPC communication) has been discovered in Citrix ADC. To mitigate this vulnerability, a configuration change is required in Citrix ADC. This configuration change is supported in the following Citrix products and firmware versions:



- Citrix ADC and Citrix Gateway 13.1-4.43 and later releases 

- Citrix ADC and Citrix Gateway 13.0-83.27 and later releases of 13.0 

- Citrix ADC and Citrix Gateway 12.1-63.22 and later releases of 12.1 

- Citrix ADC and NetScaler Gateway 11.1-65.23 and later releases of 11.1 

- Citrix ADC 12.1-FIPS 12.1-55.257 and later releases of 12.1-FIPS  

- Citrix SD-WAN WANOP Edition 11.4.2 and later releases of 11.4 

- Citrix SD-WAN WANOP Edition 10.2.9c and later releases of 10.2 

Citrix Citrix ADC security vulnerabilities mitigation steps



CVE-2021-22956 only affects access to the management GUI, Nitro API and RPC communication and does not affect CLI access. Citrix strongly recommends that network traffic to the appliance’s management interface is separated, either physically or logically, from normal network traffic. Doing so greatly diminishes the risk of exploitation of this issue. See https://docs.citrix.com/en-us/citrix-adc/citrix-adc-secure-deployment/secure-deployment-guide.html for more information. 



What Citrix customers should do

To address these vulnerabilities customers should follow all the upgrade and configuration instructions below. 



CVE-2021-22955: Affected customers must upgrade to one of the following supported versions of Citrix ADC and Citrix Gateway to address the vulnerability: 



- Citrix ADC and Citrix Gateway 13.1-4.43 and later releases  

- Citrix ADC and Citrix Gateway 13.0-83.27 and later releases of 13.0 

- Citrix ADC and Citrix Gateway 12.1-63.22 and later releases of 12.1 

- Citrix ADC and NetScaler Gateway 11.1-65.23 and later releases of 11.1 

- Citrix ADC 12.1-FIPS 12.1-55.257 and later releases of 12.1-FIPS 

Citrix recommends that affected customers install the relevant update as soon as possible. 



CVE-2021-22956: Customers must configure their appliance according to the Citrix Application Delivery Controller, Citrix Gateway, and Citrix SD-WAN WANOP Edition - Management Module Configuration Reference Guide to address the vulnerability. This configuration change is only available in the following versions: 



- Citrix ADC and Citrix Gateway 13.1-4.43 and later releases 

- Citrix ADC and Citrix Gateway 13.0-83.27 and later releases of 13.0 

- Citrix ADC and Citrix Gateway 12.1-63.22 and later releases of 12.1 

- Citrix ADC and NetScaler Gateway 11.1-65.23 and later releases of 11.1 

- Citrix ADC 12.1-FIPS 12.1-55.257 and later releases of 12.1-FIPS  

- Citrix SD-WAN WANOP Edition 11.4.2 and later releases of 11.4 

- Citrix SD-WAN WANOP Edition 10.2.9c and later releases of 10.2 

Citrix recommends that affected customers ensure they are running a relevant version and then modify the configuration as soon as their patching schedule allows. 



Sources



https://support.citrix.com/article/CTX330728



https://support.citrix.com/article/CTX331588


https://stefanos.cloud/blog/citrix-adc-security-vulnerabilities/

Comments

Post a Comment

Popular posts from this blog

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch...
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom...
Read more

FsLogix 2201 Public Preview release

Image
The FsLogix 2201 Public Preview release is now available for download from Microsoft. The change log is as follows: - Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. - The OfficeFileCache folder located at %LOCALAPPDATA%MicrosoftOffice16.0OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. - Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. - Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. - FSLogix now correctly handles cases where...
Read more