IRONSMITHINTEL
HIGHCVSS8.0
|
Actively Exploited
|CISA KEV|CVE-2024-8068|Auth: low — authenticated user|Reboot: required|Manual only

Citrix Session Recording Improper Privilege Management Vulnerability (CVE-2024-8068)

Citrix Session Recording contains an improper privilege management vulnerability that could allow for privilege escalation to NetworkService Account access. An attacker must be an authenticated user in the same Windows Active Directory domain as the session recording server domain.

Published Nov 12, 2024 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

An attacker, with a low-privilege account, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-09-15 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Improper Privilege Management (CWE-269) vulnerability in Citrix Session Recording. 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 Exploitation requires adjacent_network access, low attack complexity, a low-privilege authenticated account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

Network Security Team
Firewall Administrators
IT Security
Running session recording: v < 2407, 1912, 2203, 2402, 2407
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-08-25 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-09-15.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2024-8068's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.