← Back to blog Cybersecurity

Citrix patched the NetScaler SAML zero-day and a new one is being exploited: install the patch today and check how your Mexico operation logs in through Citrix

4 min read

Last week we wrote about two unpatched Citrix NetScaler zero-days. There is news, and not all of it is good. On October 4 Citrix released the patch for the SAML flaw in NetScaler ADC and Gateway that was already being used in attacks, as BleepingComputer reported.

One day later, on October 5, The Hacker News reported a brand new zero-day, exploited in targeted attacks, that can knock SAML deployments offline. For a foreign company with people in Mexico that means two questions today: has headquarters installed the patch, and what does the Mexico site do if the gateway goes down.

What happened and who it hits

Two flaws, one box One already has a patch and was being exploited before it. The other is new, also exploited, and can take down access for the whole company.

A zero-day is a flaw attackers use before the vendor fixes it. NetScaler is the box, physical or virtual, that people use from outside to reach the VPN, the virtual desktop or the applications of the company.

SAML is the protocol NetScaler uses to ask your identity provider (Entra ID, Okta, ADFS) whether a user is who they claim to be. If the staff at your Monterrey plant see the corporate sign-in page when they connect through Citrix, you almost certainly use SAML.

The typical setup we see: headquarters in the US or Europe runs the NetScaler, and the Mexico operation only logs in through it. Nobody local knows what version it runs. That is fine until a week like this one.

How to tell if your NetScaler uses SAML

Five minutes in the console Gateway authentication policies and the exact firmware version. That is enough to know whether you are on the list.

In the admin console, look at the authentication policies on the Gateway virtual server. A SAML action, or an advanced authentication (nFactor) flow with a SAML step, puts you on the list.

Quicker hint: ask your IT team whether the VPN username and password screen belongs to Microsoft, Okta or Google rather than Citrix. If it does, SAML is in the middle.

Also write down the exact firmware version. The Citrix bulletin lists which versions are affected and which ones carry the fix. Compare against that list, not against what somebody remembers.

The order of actions today

Patching is step one, not the only step If somebody already got in through the flaw, the patch does not kick them out. Sessions and keys have to change.
StepWhat to doWhy
1Install the Citrix patch on ADC and GatewayCloses the SAML flaw already under exploitation
2Terminate every active sessionWhoever got in stays in, patch or not
3Rotate certificates, admin passwords and service accountsThey may have been copied before the patch
4Review access logs from the last few weeksLogins at odd hours or from countries where you have no staff
5Look for new accounts and new administratorsThe favorite way to leave a door open

Patching without ending sessions is changing the lock and leaving the window open. The same logic applied to remote access tools in general.

The second zero-day, still without a patch

According to The Hacker News, this flaw can knock SAML deployments offline. It does not need to steal anything to hurt you: it is enough that at 8 a.m. nobody at the plant can reach the VPN.

Until Citrix ships the fix, there are three paths:

  • Limit who can reach the NetScaler from the internet. If your Mexico staff connect from fixed offices, filter by IP on the firewall.
  • Disable SAML temporarily and fall back to LDAP authentication with a second factor. Uncomfortable, but you keep working.
  • Segment: let the NetScaler see only the servers it publishes, not the whole network. If it goes down, access goes down, not the company.

Our opinion: if the NetScaler is the only door into your Mexico operation, build the plan B this week, not the day it fails. In Mexico that plan B usually means someone local who can get people working again while headquarters sleeps.

How ProcessBi helps

Under an IT support plan the NetScaler goes into the inventory like any other server: we know what version it runs, we follow the Citrix bulletins and we apply the patch in an agreed window, with a prior backup and a rollback plan.

After the patch we do the part almost nobody does: end sessions, rotate keys and read the logs. We work remotely in English or Spanish, and when the appliance sits in a Mexico data center we can send local hands for the physical part.

ProcessBi technician working on a NetScaler in a Mexico rack
If your Mexico team logs in through Citrix, today is patch day. Tell us your case. Foto: Pexels

What about your Mexico operation?

If you do not know what version your NetScaler runs, or if the integrator who installed it is long gone, that is the first task of the day.

We offer a free assessment: version, patch status, SAML usage and what plan B your Mexico site has if the second flaw arrives before its fix.

Book your free assessment — we reply the same business day.

Your path

Running IT in Mexico from abroad

44 of 51
  1. Smart hands ✓ Read You are here 2 min
  2. Remote support ✓ Read You are here 3 min
  3. Nearshoring checklist ✓ Read You are here 2 min
  4. Retail rollouts ✓ Read You are here 2 min
  5. Fake IT support ✓ Read You are here 3 min
  6. Backups that restore ✓ Read You are here 3 min
  7. Secure M365 ✓ Read You are here 3 min
  8. Windows 10 deadline ✓ Read You are here 4 min
  9. Audit app access ✓ Read You are here 3 min
  10. CEO fraud ✓ Read You are here 4 min
  11. Office 2016 cutoff ✓ Read You are here 3 min
  12. Patch today ✓ Read You are here 4 min
  13. Patch VMware ✓ Read You are here 4 min
  14. Office 2021 EOL ✓ Read You are here 3 min
  15. Starlink for sites ✓ Read You are here 3 min
  16. Cardless access ✓ Read You are here 4 min
  17. Control AI on PCs ✓ Read You are here 4 min
  18. ScreenConnect flaw ✓ Read You are here 4 min
  19. Server 2022 EOL ✓ Read You are here 3 min
  20. Exposed cameras ✓ Read You are here 3 min
  21. Domain trust fix ✓ Read You are here 4 min
  22. Patch Cisco ISE ✓ Read You are here 3 min
  23. Protect the plant ✓ Read You are here 3 min
  24. Move to 25H2 ✓ Read You are here 4 min
  25. Outages and UPS ✓ Read You are here 3 min
  26. IT maintenance ✓ Read You are here 4 min
  27. Third-party scripts ✓ Read You are here 3 min
  28. License audit ✓ Read You are here 4 min
  29. Bajío fiber corridor ✓ Read You are here 3 min
  30. Check Point flaw ✓ Read You are here 4 min
  31. Cashless payments ✓ Read You are here 3 min
  32. AI that hacks alone ✓ Read You are here 3 min
  33. Zyxel and Veeam today ✓ Read You are here 4 min
  34. Aeromexico breach ✓ Read You are here 4 min
  35. MikroTik router ✓ Read You are here 3 min
  36. Guest Wi-Fi ✓ Read You are here 4 min
  37. Citrix zero-days ✓ Read You are here 4 min
  38. Protect your plant ✓ Read You are here 3 min
  39. TeamViewer patch ✓ Read You are here 4 min
  40. SD-WAN zero-day ✓ Read You are here 4 min
  41. FortiMail zero-day ✓ Read You are here 4 min
  42. M365 billing ✓ Read You are here 4 min
  43. SAT-IMSS breach ✓ Read You are here 4 min
  44. NetScaler patch ✓ Read You are here 4 min
  45. Cutting access ✓ Read You are here 3 min
  46. Patch today ✓ Read You are here 4 min
  47. ESU price hike ✓ Read You are here 3 min
  48. Invoicing continuity ✓ Read You are here 3 min
  49. Fake QR codes ✓ Read You are here 4 min
  50. Default passwords ✓ Read You are here 3 min
  51. Shadow AI rules ✓ Read You are here 3 min
  52. Field services →
Next An engineer locked 3,000 devices on their own employer's network: how to cut access when the IT admin or vendor at your Mexico site leaves