Is it CitrixBleed4? Well no. Is it good? Also no. Citrix Net... #1571
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Context
While reproducing CitrixBleed2 (CVE-2025-5777), watchTowr Labs found two Citrix NetScaler issues: (1) WT-2025-0089, a configuration-induced memory leak (no CVE), and (2) WT-2025-0090, a reflected XSS via SAML RelayState, assigned CVE-2025-12101.
Background: How AAA works on NetScaler
AAA stands for Authentication, Authorization, and Auditing. It authenticates users (e.g., password or SAML), applies access rules, and logs sessions. Admins typically create an...
🔧 Technical Details
Misconfiguration-induced memory disclosure. If an AAA virtual server is created but the AAA feature is not enabled via CLI, requesting the root path “/” can trigger an error page that includes leaked process memory. The trick is to induce unsupported feature states to push appliances into memory-leaking error paths.
RelayState-based header/body injection → rXSS. In SAML flows that base64-decode and reflect
RelayState, prepend newline characters and inject aContent-Type: text/htmlheader followed by HTML/JS. After URL-encoding and base64-encoding this sequence, place it inRelayStateand POST alongside a validSAMLResponseto the SSO endpoint (e.g.,/cgi/logout) to force the response to render attacker-controlled HTML, achieving reflected XSS.CSRF delivery pattern. Host a page that auto-submits a cross-origin POST containing a syntactically valid
SAMLResponseand the craft...🤖 Agent Actions
I analyzed the blog and HackTricks and updated the most relevant section with the new technique.
What I added
Why here
Notes
Changes applied
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.