dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-8885

HIGH · 8.8 CVSS v3.1 Published 2024-10-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

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 · unedited
A local privilege escalation vulnerability in Sophos Intercept X for Windows with Central Device Encryption 2024.2.0 and older allows writing of arbitrary files.

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 · moderate confidence

A local privilege escalation vulnerability in Sophos Intercept X for Windows with Central Device Encryption versions 2024.2.0 and older allows unprivileged local attackers to write arbitrary files to the filesystem, likely enabling escalation to SYSTEM or administrator privileges through overwriting sensitive system files or executables.

MitigationUpdate Sophos Intercept X for Windows with Central Device Encryption to a version newer than 2024.2.0 per vendor advisory.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Sophos Intercept X installation
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\SAV\ or check Program Files for Sophos folder. Alternatively, run 'wmic product get name,version' or 'Get-WmiObject Win32_Product' in PowerShell to list installed Sophos products.
    Affected if Sophos Intercept X for Windows is not found, meaning the product is not installed and this CVE does not apply.
  2. Confirm Central Device Encryption component
    Check if the Central Device Encryption (CDE) component is present. Look for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\SAV\Customers\ or inspect the Sophos installation directory for CDE-related DLLs and services.
    Affected if The Central Device Encryption component is not installed; without CDE, this specific vulnerability path may not be applicable.
  3. Identify installed version
    Check the installed version via: 1) Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\SAV\Version (or similar Sophos product key), 2) Right-click the Sophos icon in system tray and select 'About', or 3) Run 'sophosdiag.exe' if available to generate a diagnostic report containing version info.
    Affected if The installed version is 2024.2.0 or any version older than 2024.2.0, indicating the system is running a vulnerable version.
  4. Confirm version is within affected range
    Compare the identified version number to the affected range: 2024.2.0 and older. Version 2024.2.0 itself is confirmed vulnerable. Any version newer than 2024.2.0 is not affected by this specific CVE.
    Affected if The installed version is 2024.2.0 or older - the environment is affected by this privilege escalation vulnerability.

The environment is affected if Sophos Intercept X for Windows with Central Device Encryption is installed and the installed version is 2024.2.0 or any older version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Sophos Intercept X for Windows with Central Device Encryption to a version newer than 2024.2.0 per vendor advisory.

Recommended fix Moderate confidence

Latest version of Sophos Intercept X for Windows with Central Device Encryption (version higher than 2024.2.0)

  1. 1. Verify the currently installed version of Sophos Intercept X for Windows with Central Device Encryption by opening the Sophos Central admin console or checking the local endpoint protection status.
  2. 2. If the installed version is 2024.2.0 or older, initiate an upgrade to the latest available version.
  3. 3. Deploy the upgrade through Sophos Central Device Encryption management console or push the update to affected endpoints.
  4. 4. After deployment, verify the new version is installed and confirm the vulnerability is resolved.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8885 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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