CVE Intelligence
Skip to main content
HIGH

CVE-2022-1824

CVE-2022-1824 — McAfee MCPR privilege escalation

An uncontrolled search path vulnerability in McAfee Consumer Product Removal Tool prior to version 10.4.128 could allow a local attacker to perform a sideloading attack by using a specific file name. This could result in the user gaining elevated permissions and being able to execute arbitrary code as there were insufficient checks on the executable being signed by McAfee.

Published Updated Sources: cvelistV5, trellix

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

mcafee

mcafee_consumer_product_removal_tool

CVSS base

7.9

HIGH

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (1)

mcafee consumer product removal tool

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.9CVSS 3.1HIGHcvelistV5

Weakness & attack patterns

  • CWE-427

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
  • T1574.009Hijack Execution Flow: Path Interception by Unquoted Path
  • T1574.001Hijack Execution Flow: DLL search order hijacking

References

1 on the record

Elsewhere on this site

  • mcafeeevery CVE for this vendor
  • CWE-427other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.