CVE-2022-1823
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 · uneditedImproper privilege management vulnerability in McAfee Consumer Product Removal Tool prior to version 10.4.128 could allow a local user to modify a configuration file and perform a LOLBin (Living off the land) attack. This could result in the user gaining elevated permissions and being able to execute arbitrary code, through not correctly checking the integrity of the configuration file.
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 · high confidenceThis is a local privilege escalation vulnerability in McAfee Consumer Product Removal Tool where a local user can modify a configuration file without integrity checks, enabling a LOLBin (Living off the Land) attack to execute arbitrary code with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.4.128CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check if McAfee Consumer Product Removal Tool is installedLook for the tool in Program Files or Program Files (x86) directories, or check installed programs list via Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if The tool is present on the system
-
Identify installed version of McAfee Consumer Product Removal ToolCheck the version of the executable file (typically named MCPR.exe or similar) by right-clicking the file, selecting Properties, and viewing the Details tab, or use command: dir /s "*MCPR*.exe" and check version with: wmic datafile where "name='PATH\TO\FILE'" get VersionAffected if The version is lower than 10.4.128
-
Locate configuration files used by the toolSearch the McAfee Consumer Product Removal Tool installation directory for configuration files (typically .xml, .ini, .cfg, or .config files)Affected if Configuration files exist in the installation directory
-
Check configuration file permissionsRight-click the configuration file, select Properties, then Security tab. Check if standard users have Write or Modify permissions to the file.Affected if Standard users have Write or Modify permissions to configuration files in the tool's directory
A user is affected if McAfee Consumer Product Removal Tool version is below 10.4.128 AND configuration files in the tool's directory are writable by non-privileged users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.4.128
Upgrade McAfee Consumer Product Removal Tool to version 10.4.128 or later to obtain the fixed version with proper configuration file integrity validation.
10.4.128 or later
- Obtain McAfee Consumer Product Removal Tool version 10.4.128 or later from an official McAfee source such as service.mcafee.com
- Download the updated installer for the Consumer Product Removal Tool
- Run the installer to upgrade the tool to version 10.4.128 or later
- Verify the installed version matches the fixed release (10.4.128 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-1823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1823 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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