CVE-2022-27180
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 · uneditedUncontrolled search path in the Intel(R) MacCPUID software before version 3.2 may allow an authenticated user to potentially enable escalation of privilege via local access.
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 confidenceThis is an uncontrolled search path element (DLL/library hijacking) vulnerability in Intel MacCPUID software prior to version 3.2. An authenticated local user can place malicious DLLs or other executable resources in a directory that the application searches during runtime, causing the application to load and execute them with elevated privileges, achieving local privilege escalation.
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< 3.2CVSS 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 Intel MacCPUID is installedSearch for the MacCPUID application on the system. On macOS, check /Applications folder or use Spotlight search. On Windows, check Program Files directories.Affected if Intel MacCPUID software is found on the system
-
Identify the installed versionRight-click the MacCPUID application, select Get Info (macOS) or Properties (Windows), and locate the version number. Alternatively, launch the application and check any About or version information within the GUI.Affected if The displayed version number is lower than 3.2 (for example, 3.1, 3.0, or earlier)
-
Verify if application runs with elevated privilegesCheck the application permissions or launch configuration. On macOS, examine the application bundle for signed executables and check if it requires admin privileges to run. On Windows, check if the application is configured to run as administrator.Affected if The application runs with elevated or administrator privileges, allowing it to load libraries from user-controlled directories
-
Inspect application directory for writable locationsExamine the directory where MacCPUID is installed. Check if any subdirectories or common DLL search paths are writable by non-privileged users, which would allow placement of malicious libraries.Affected if Non-privileged users have write access to directories in the application DLL search path
A user is affected if Intel MacCPUID is installed with a version lower than 3.2 and the application executes with elevated privileges, enabling a local authenticated attacker to perform DLL hijacking for privilege escalation.
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 · scoped3.2
Update Intel MacCPUID software to version 3.2 or later, which contains the vendor's patch addressing the uncontrolled search path vulnerability.
MacCPUID version 3.2 or later
- Navigate to the official Intel website and download MacCPUID version 3.2 or later
- Uninstall the current version of MacCPUID if already installed
- Install the newly downloaded version 3.2 or later
- Restart the application if it was running during the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27180 — 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-27180 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