Note: articles are for educational purposes and are not professional security advice — consult an expert for your specific needs.

Addressing Cyberattacks on Citrix Devices Through NetScaler Vulnerability Exploitation

In short

Citrix NetScaler ADC and Gateway code injection flaw CVE-2023-3519 enables unauthenticated remote code execution and has been exploited to steal credentials through modified login pages. Apply Citrix’s July 2023 patches, reimage compromised hosts and issue new credentials. Clean rc.netscaler if attackers used it to restore a web shell on reboot.

Summary written with AI from this article, and checked against it.

CVE-2023-34048: An In-depth Analysis of VMware's Critical Vulnerability in vCenter Server and its Patches

At a glanceCVE-2023-3519

CVE-2023-3519 has a CVSS 3.1 base score of 9.8 (Critical) from NVD. It is fixed in Citrix netscaler application delivery controller 12.1-55.297, 13.0-91.13, 13.1-37.159 and 13.1-49.13.

Severity9.8 Critical (CVSS 3.1, NVD)
Fixed inCitrix netscaler application delivery controller 12.1-55.297, 13.0-91.13, 13.1-37.159, 13.1-49.13
AffectedCitrix netscaler application delivery controller 12.1 – before 12.1-55.297; 13.0 – before 13.0-91.13; 13.1 – before 13.1-37.159; 13.1 – before 13.1-49.13
ExploitedYes: in CISA's Known Exploited Vulnerabilities catalog since July 19, 2023
EPSS99.7% chance of exploitation in the next 30 days (FIRST, October 27, 2026)
Public exploitpacketstormsecurity.com, packetstormsecurity.com · 13 GitHub repositories name it: proofs of concept, scanners, detections. Unverified: some are fake or malicious.
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
WeaknessCWE-94 Code Injection
UbuntuListed, no packages yet
DebianListed, no packages yet
Red HatNot tracked yet
Also inCitrix netscaler gateway

Is there a public exploit for CVE-2023-3519?

Yes: CVE-2023-3519 is exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on July 19, 2023. NVD links 2 exploit references and 13 public GitHub repositories name it: proofs of concept, scanners and detections. None of it is verified: some such repositories are fake or carry malware, so read the code before running it, and only against systems you own. FIRST's EPSS puts the chance of exploitation in the next 30 days at 99.7%, higher than 99.9% of scored CVEs.

From NVD, Ubuntu, Debian · checked October 28, 2026

A critical vulnerability in Citrix NetScaler ADC and Gateway devices has been the focal point of an extensive cyberattack campaign aimed at stealing user credentials. IBM identified "at least 600 unique victim IP addresses hosting modified NetScaler Gateway login pages," primarily situated in the United States and Europe. This article delves into the technical intricacies of the vulnerability, its exploitation, and provides recommendations to counter the threat.

Technical Overview of the Vulnerability

CVE-2023-3519, designated with a CVSS score of 9.8, pertains to a severe code injection vulnerability. Patched by Citrix in July 2023, this flaw could enable unauthenticated remote code execution. For several months, attackers have leveraged this vulnerability to compromise susceptible devices and gain persistent access for future attacks.

Modus Operandi of the Attacks

IBM X-Force discovered this malicious activity. The attackers exploited the NetScaler vulnerability to insert a malevolent script into the HTML content of the authentication web page. This maneuver allows them to capture user credentials. Specifically, they deployed a web shell based on PHP to execute their malicious activities. This PHP web shell enabled them to insert custom code into the NetScaler Gateway login page. This custom code included a reference to a remotely hosted JavaScript file controlled by the attackers.

The Role of JavaScript in Data Harvesting

The embedded JavaScript code aimed to harvest form data containing usernames and passwords. When users attempted to authenticate themselves, this JavaScript code activated and sent the harvested credentials to a remote server via an HTTP POST method.

Recommendations for Countermeasures

  1. Prompt Patch Application: Organizations should immediately apply patches to mitigate this vulnerability.
  2. Change of Credentials: All default login credentials should be changed, given that the configuration files of NetScaler contain multiple credentials and certificates.
  3. Incident Response Measures: Organizations should enact a series of incident response protocols:
    • Quarantine or disconnect potentially compromised hosts.
    • Reimage hosts that have been compromised.
    • Issue new account credentials.
    • Inspect artifacts like running processes, unusual authentications, and recent network activities.
  4. Cleaning rc.netscaler: If the threat actor used /lash/nsconfig/rc.netscaler to rewrite a web shell during each reboot, it’s imperative to clean the rc.netscaler file as mentioned by the Cybersecurity and Infrastructure Security Agency (CISA).

Final Thoughts

The commencement date of this cyberattack campaign remains uncertain. However, the first observed alteration to a login page occurred on August 11, 2023. This suggests that the campaign has been active for around two months. Interestingly, no specific threat actor or group has yet been definitively linked to this campaign. Given the high CVSS score and the significant number of affected IP addresses, this issue warrants urgent attention and remediation efforts from organizations.

Source

  1. CVE recordCVE-2023-3519 in the National Vulnerability Database · nvd.nist.gov
Vishal

About the author

· Software & security engineer

GitHub · LinkedIn · X

Vishal writes Trickyworld's tutorials and interview-preparation guides on programming, databases, cyber security and AI. Vishal has been shipping production software long enough to have firm opinions about Python, PHP, Node.js, and JavaScript, and to have been wrong about each of them at least once. The work has run the whole stack: Drupal and Laravel applications, React front ends, MySQL and MongoDB underneath, Redis and Memcached for the things that had to be fast, Apache Solr for the things that had to be findable. That last part turned out to matter more than anyone expected. Tune a Solr index for a season, then watch a language model confidently retrieve the wrong document, and you recognise an old problem wearing new clothes. Most of what is hard about AI systems is not the model. It is retrieval, caching, latency budgets, and deciding what the system does when the answer comes back wrong — which is work he has been doing since well before anyone called it AI engineering. He plays a lot of games, which is less a hobby disclosure than an admission of where a good share of his engineering instinct came from. Real-time systems with a frame budget. State that has to stay coherent while a player does something no designer anticipated. The permanent question of what happens when the frame cannot finish in time. Those habits carry over more directly than they have any right to. He has written several books on programming, all built on the same conviction: most technical writing is unclear because the author never decided what to leave out. More from Vishal → · Editorial policy

#Citrix NetScaler#Code Injection#Credential Harvesting#CVE-2023-3519#Cyberattacks#IBM X-Force#incident response#remote code execution#Security Patch

More on Computer Tricks.

Latest articles

$ subscribe --weekly

Get the next tutorial in your inbox.

Programming, security and AI — the practical bits, no spam. Unsubscribe any time.