CVE-2025-60349: An issue was discovered in Prevx v3.0.5.220 allowing attackers to cause a denial of service via sending IOC...
An issue was discovered in Prevx v3.0.5.220 allowing attackers to cause a denial of service via sending IOCTL code 0x22E044 to the pxscan.sys driver. Any processes listed under registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\pxscan\Files will be terminated.
Security readout for executives and security teams
Plain-English summary
CVE-2025-60349 is a denial-of-service issue in Prevx v3.0.5.220. The reported impact is forced termination of processes listed in a pxscan registry key, which could disrupt endpoint security or business applications if those systems use this driver.
Executive priority
Treat as high priority for any environment still running this Prevx version. First determine whether the product exists in the estate; urgency drops materially if it is absent.
Technical view
The CVE describes improper resource control involving the pxscan.sys driver. Sending IOCTL 0x22E044 reportedly causes termination of processes under HKLM\System\CurrentControlSet\Services\pxscan\Files. CVSS 3.1 is 7.5 high with availability-only impact. No CPEs or vendor patch details are provided in the bundle.
Likely exposure
Exposure appears limited to systems running Prevx v3.0.5.220 with the pxscan.sys driver present. The source bundle does not identify other affected versions, products, or supported platforms.
Exploitation context
The CVE is not listed as KEV in the provided data. A public GitHub reference exists, but the bundle does not provide evidence of active exploitation in the wild.
Researcher notes
Evidence is narrow and incomplete: affected metadata is n/a, no CPEs are listed, and no patch is named. The core claim is process termination through a driver IOCTL, mapped to CWE-400.
Mitigation direction
Inventory endpoints for Prevx v3.0.5.220 and pxscan.sys.
Check vendor or maintainer guidance for updates or removal instructions.
Prioritize mitigation on systems protecting critical applications or services.
Monitor for unexpected termination of registry-listed processes.
Avoid disabling the driver without operational and vendor review.
Validation and detection
Confirm whether Prevx v3.0.5.220 is installed.
Verify whether pxscan.sys is loaded or present.
Review the pxscan\Files registry key for critical process entries.
Check endpoint logs for unexplained process terminations.
Track CVE and vendor references for updated remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.