CVE-2024-13972
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability related to registry permissions in the Intercept X for Windows updater prior to Core Agent version 2024.3.2 can lead to a local user gaining SYSTEM level privileges during a product upgrade.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA registry permissions vulnerability in the Intercept X for Windows updater (versions prior to Core Agent 2024.3.2) allows a local authenticated user to manipulate registry keys during product upgrades to gain SYSTEM-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Intercept X Core Agent versionOpen Windows Settings > Apps > Apps & Features, or run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to find the installed version of Intercept X Core AgentAffected if The installed version is present but earlier than 2024.3.2
-
Verify the updater component existsCheck if the Deep Security or Intercept X updater service is installed. Run 'Get-Service | Where-Object {$_.DisplayName -like "*Deep Security*" -or $_.DisplayName -like "*Intercept X*"}' or look for updater-related services in Services.mscAffected if The updater service exists and the agent version is below 2024.3.2
-
Inspect registry key permissionsExamine registry keys under HKLM\SOFTWARE\Sophos or the product's registry location for the updater. Use regedit or 'Get-Acl HKLM:\SOFTWARE\* | Select-Object Path, Owner, AccessToString' to check if standard users have write permissions to updater-related keysAffected if Non-admin users have write or modify access to updater registry keys and the agent version is below 2024.3.2
You are affected if Intercept X Core Agent for Windows is installed with a version earlier than 2024.3.2 and the updater registry keys permit modifications by authenticated local users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Intercept X Core Agent to version 2024.3.2 or later to remediate the registry permission vulnerability.
Core Agent version 2024.3.2 or later
- Verify the current version of Sophos Intercept X Core Agent installed on the system
- Initiate an update through the Sophos Central management console, or run a local update check within the Intercept X agent
- Upgrade to Core Agent version 2024.3.2 or later to remediate the registry permission vulnerability
- Confirm the upgrade completed successfully and verify the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13972 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13972 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data