dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-8424

HIGH · 8.5 CVSS v4.0 Published 2024-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
Improper Privilege Management vulnerability in WatchGuard EPDR, Panda AD360 and Panda Dome on Windows (PSANHost.exe module) allows arbitrary file delete with SYSTEM permissions.

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

Improper Privilege Management vulnerability in the PSANHost.exe module of WatchGuard EPDR, Panda AD360, and Panda Dome on Windows allows a local attacker to delete arbitrary files with SYSTEM privileges due to insufficient access controls on the file deletion functionality.

MitigationApply vendor-supplied patches for WatchGuard EPDR, Panda AD360, and Panda Dome when released. Until then, restrict local user permissions to PSANHost.exe and monitor for suspicious file deletion activity.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify if WatchGuard EPDR, Panda AD360, or Panda Dome is installed
    Check for the presence of the product via installed programs list, or look for PSANHost.exe process in Task Manager or via command: tasklist | findstr -i PSANHost
    Affected if Any of these products are installed and the PSANHost.exe process is running
  2. Determine the installed product version
    Check the version of the installed product through the application itself, Windows Programs and Features, or by right-clicking the executable and viewing Properties. For WatchGuard EPDR, check the EPDR console or installed version. For Panda products, check Panda's system tray icon or program information.
    Affected if The installed version is lower than 8.00.23.0000 for EPDR/AD360, or lower than 22.03.00 for Panda Dome
  3. Verify PSANHost.exe service exists and runs with elevated privileges
    Open Services (services.msc), locate the PSANHost service, right-click and select Properties. Check the executable path and verify it runs under the SYSTEM account or a privileged account.
    Affected if The PSANHost service is configured to run with SYSTEM or elevated privileges and the product version is vulnerable
  4. Confirm the product is not patched to the fixed version
    Compare your installed version against the fixed releases: EPDR 8.00.23.0000, Panda AD360 8.00.23.0000, Panda Dome 22.03.00. Use the product's built-in about or version information.
    Affected if The installed version is known and falls below any of the three fixed version thresholds

You are affected if WatchGuard EPDR, Panda AD360, or Panda Dome is installed with PSANHost.exe running under SYSTEM privileges and the version is below 8.00.23.0000 for EPDR/AD360 or below 22.03.00 for Panda Dome.

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

Apply vendor-supplied patches for WatchGuard EPDR, Panda AD360, and Panda Dome when released. Until then, restrict local user permissions to PSANHost.exe and monitor for suspicious file deletion activity.

Recommended fix High confidence

EPDR: upgrade to 8.00.23.0000 or later; Panda AD360: upgrade to 8.00.23.0000 or later; Panda Dome: upgrade to 22.03.00 or later

  1. 1. Identify the currently installed version of WatchGuard EPDR, Panda AD360, or Panda Dome on the affected Windows system
  2. 2. Navigate to the official WatchGuard support portal at www.watchguard.com to obtain the corrected version
  3. 3. Download the appropriate fixed release: EPDR version 8.00.23.0000 or later, Panda AD360 version 8.00.23.0000 or later, or Panda Dome version 22.03.00 or later
  4. 4. Review the vendor release notes for any specific upgrade instructions or注意事项
  5. 5. Apply the upgrade following WatchGuard's standard installation or update procedures
  6. 6. Verify the PSANHost.exe module has been updated to the fixed version after installation
  7. 7. Confirm the vulnerability is remediated by ensuring the arbitrary file deletion with SYSTEM privileges is no longer possible
Caveat Review WatchGuard release notes for any product-specific upgrade considerations or known issues before applying

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8424 — 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-8424 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