CVE-2024-8068
Privilege escalation to NetworkService Account access in Citrix Session Recording when an attacker is an authenticated user in the same Windows Active Directory domain as the session recording server domain
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attacker must be an authenticated user in the same Windows Active Directory domain, indicating local or internal network access rather than an HTTP request. Therefore, a web application firewall cannot filter or block this attack.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-8068 being exploited?
Yes. CVE-2024-8068 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-8068?
CVE-2024-8068 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-8068?
Yes. A fix has been recorded for CVE-2024-8068. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-8068 affect?
CVE-2024-8068 affects citrix:session_recording. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 2407 Current Release and < 24.5.200.8
- affected>= 1912 LTSR and < CU9 hotfix 19.12.9100.6
- affected>= 2203 LTSR and < CU5 hotfix 22.03.5100.11
- affected>= 2402 LTSR and < CU1 hotfix 24.02.1200.16
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 26 Aug 2025 (SSVC 2.0.3).
timeline
- 12 Nov 2024Published
- 25 Aug 2025Added to CISA KEV (exploited in the wild) · 285 days (about 10 months) later
- 26 Aug 2025CISA SSVC assessment: exploitation active · 1 day later
- 15 Sept 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 37 days later
- 19 Aug 2026First proof-of-concept repository on GitHub (unvetted) · 301 days (about 10 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 76 days (about 3 months) later
- Linksupport.citrix.com /s/article/CTX691941-citrix-session-recording-security-bulletin-for-cve20248068-
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-8068
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.