LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-60349 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-60349Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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.