Safeguard
Vulnerability Analysis

Citrix Bleed (CVE-2023-4966): Stolen Sessions That Walked Past MFA

A factual look at Citrix Bleed, a 2023 buffer over-read in NetScaler appliances that leaked valid session tokens, allowing attackers to hijack authenticated sessions without credentials or a second factor.

Safeguard Research Team
2 min read

Citrix Bleed (CVE-2023-4966): Stolen Sessions That Walked Past MFA

Summary

Citrix Bleed, CVE-2023-4966, is a vulnerability in Citrix NetScaler ADC and NetScaler Gateway disclosed in October 2023. It was exploited in the wild, including in ransomware campaigns, and CISA issued advisories after significant exploitation against organisations across sectors.

Technical Root Cause

The vulnerability is a buffer over-read (CWE-125), the same broad class as Heartbleed, from which it takes its nickname. A crafted request to an affected appliance caused it to return more memory than intended in its response, and that memory could contain valid session tokens belonging to authenticated users.

The consequence is what made it severe. An attacker who obtained a valid session token did not need to authenticate at all: they could replay the token and inherit an existing authenticated session. Multi-factor authentication happens during authentication, so a hijacked post-authentication session bypassed it entirely.

Why It Mattered

Patching alone was insufficient, which caught many organisations out. Because sessions established before patching remained valid afterwards, remediation required terminating all active sessions on affected appliances in addition to applying the fix. Organisations that patched without invalidating sessions could remain compromised through tokens already stolen.

OWASP / CWE Mapping

  • CWE-125: Out-of-bounds Read
  • OWASP A07:2021: Identification and Authentication Failures
  • Related to CWE-384: Session Fixation, in effect if not mechanism

Lasting Impact

Citrix Bleed is the standard example that MFA protects the authentication event, not the session that follows it, and that incident response for a session-disclosure bug has a mandatory second step beyond patching. It also illustrated that edge appliances, which sit at the network boundary by design and are often excluded from normal endpoint tooling, are high-value targets.

How Safeguard Helps

Vulnerability tracking against known-exploited catalogues is what surfaces an appliance CVE like this quickly. The session-invalidation step, however, is a response procedure rather than a scanning finding, and is worth encoding explicitly in runbooks for any vulnerability classed as token or session disclosure.

References

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.