Threats / Citrix / CVE-2024-8068
CVE-2024-8068
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Citrix Session Recording vulnerability
Citrix Session Recording contains an improper privilege management vulnerability allowing authenticated domain users to escalate privileges to NetworkService Account access.
Verdict
Today item — known-exploited.
An authenticated attacker within the same Windows Active Directory domain can exploit improper privilege controls in Citrix Session Recording to gain elevated NetworkService Account privileges, potentially compromising system integrity and sensitive data.
CISA KEV Yes · 2025-08-255EPSS 0.01395 (verify live)6CVSS 5.13CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-08-25).
Probability (EPSS)
EPSS 0.01395 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.1 (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) · Affected: Citrix, Session Recording. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-269 Improper Privilege Management — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 286 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I authenticate to the domain as a standard user with access to the Session Recording server.
Business
Attacker gains initial foothold within the trusted domain perimeter.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I identify and exploit the improper privilege management flaw in Session Recording to escalate my access level.
Business
Privilege boundary controls fail, allowing lateral movement beyond intended user scope.
3
Lateral reach — past segmentation narrative 3
Attacker
I obtain NetworkService Account privileges on the Session Recording server.
Business
Attacker gains system-level capabilities to access, modify, or exfiltrate recorded sessions and sensitive communications.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by CitrixCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.