CVE-2024-8068VulnerabilityPublished 12 Nov 2024Updated 21 Oct 2025

CVE-2024-8068: Citrix Session Recording · Improper Privilege Management

Affects Citrix Session RecordingSource CVE Database V5

Exploited in the wild · KEV due 15 Sep 2025 · 3% EPSS : apply the vendor's fix or mitigations to Citrix Session Recording now.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 15 Sep 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 3.4% chance of exploitation in 30 days – higher than 89% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 12 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 286 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Citrix
2024-08-2123:22Z, 83 days before disclosure
CVE published
on cve.org
2024-11-1217:49Z, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2025-08-25, 286 days after disclosure
KEV remediation due
US federal deadline
2025-09-15, 307 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Check the firmware or software version for Citrix Session Recording in the device's admin interface against the vendor advisory.

Description

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

Impact

The primary impact of CVE-2024-8068 is unauthorized privilege escalation within enterprise environments using Citrix Session Recording. An attacker who already has authenticated access to the domain can leverage this vulnerability to gain NetworkService-level privileges, which are significantly higher than typical user accounts. This can lead to unauthorized access to sensitive session recordings, manipulation or deletion of recorded data, and potential compromise of the session recording infrastructure. Elevated privileges may also enable attackers to move laterally within the network, escalate further privileges, or disrupt monitoring and auditing capabilities. The confidentiality and integrity of monitored sessions are at risk, which can undermine compliance and security monitoring efforts. Organizations relying on Citrix Session Recording for regulatory or security purposes may face increased risk of insider threats or external attackers exploiting compromised credentials. Although no availability impact is directly indicated, the compromise of session recording systems could indirectly affect incident response and forensic investigations. The medium severity rating suggests that while exploitation requires some level of authenticated access, the potential damage within a compromised domain environment is significant.

Mitigation

1. Monitor Citrix’s official channels for patches or updates addressing CVE-2024-8068 and apply them promptly once released. 2. Restrict access to the Citrix Session Recording server and related services to only necessary and trusted users, minimizing the number of domain accounts with access. 3. Implement strict Active Directory privilege management and segmentation to limit the ability of authenticated users to escalate privileges or access sensitive systems. 4. Employ network segmentation to isolate the session recording infrastructure from general user networks, reducing exposure to potential attackers. 5. Audit and monitor logs for unusual access patterns or privilege escalations related to the session recording service. 6. Use multi-factor authentication (MFA) for domain accounts with access to critical infrastructure to reduce the risk of credential compromise. 7. Regularly review and harden permissions on service accounts, including NetworkService, to limit their scope and capabilities where feasible. 8. Conduct internal penetration testing and vulnerability assessments focusing on privilege escalation paths within the Active Directory environment and Citrix infrastructure. 9. Educate administrators and security teams about this vulnerability to ensure rapid detection and response to suspicious activities.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 04:00 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats