@GossiTheDog@cyberplace.social
2026-10-04 09:55 UTC
Replies (4)
-
@GossiTheDog@cyberplace.social 2026-10-05 10:14
I need @watchTowr@infosec.exchange to fact-check me here but I think CVE-2026-88779 is a redux of CVE-2026-8452? At least based on this mitigation Citrix support are giving out, somebody posted it on their blog. https://www.deyda.net/index.php/de/2026/08/28/netscaler-cve-checkliste-updates-sicherheitspruefung-und-incident-response/ The 8452 patch locked SAML PrefixList to 512 byte or below string. But I think CVE-2026-88779 may be more than 15 items in PrefixList, space-separated, to trigger a vuln. Assuming Citrix support gave out the right mitigation.
-
@faebudo@ioc.exchange 2026-10-04 10:21
@GossiTheDog@cyberplace.social Also their CVSS 4.0 calculation only has VA:H, both VC and VI are None. So either they're lying or they didn't fix all the vulnerabilities used in this attack but only the triggering DoS condition but not the one leading to RCE.
-
@bontchev@infosec.exchange 2026-10-04 11:28
@GossiTheDog@cyberplace.social What resources are the attackers accessing? Not only for this exploit but for Citrix Netscaller exploits in general. I'm running a honeypot for it but it was seen only 3 hits for the past 5 years. It is geared towards a specific exploit, though - it looks only for attackers trying to access /vpn. So, I was wondering if I could expand it to catch the newer exploits, too.
-
@wdormann@infosec.exchange 2026-10-04 12:16
@GossiTheDog@cyberplace.social There's no way a memory overflow could lead to RCE on a system with no ASLR or stack canaries. 😂