CVE-2022-46646
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 · uneditedExposure of sensitive information to an unauthorized actor for some Intel Unison software may allow an authenticated user to potentially enable information disclosure 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 confidenceIntel Unison software contains a vulnerability that allows an authenticated user with local access to potentially view sensitive information they are not authorized to access. The issue is classified as an information disclosure vulnerability with a CVSS score of 5.5, indicating moderate severity.
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< 20.14.5683.0< 20.14.4244< 20.14.2.3053CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify Intel Unison software is installedCheck for Intel Unison in installed programs: On Windows, open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Unison*"}' in PowerShell. On macOS, check /Applications folder or run 'system_profiler SPApplicationsDataType | grep -i unison'.Affected if Intel Unison is found installed on the system
-
Determine installed Intel Unison versionOpen Intel Unison application and navigate to Help > About, or check the version in Programs and Features. On Windows, also try: 'Get-ItemProperty "C:\Program Files\Intel\Unison\Unison.exe"' for file version properties.Affected if Unable to determine version number (may indicate very old or very new installation)
-
Compare version against affected rangesCompare your installed version number to the following thresholds: 20.14.5683.0, 20.14.4244, and 20.14.2.3053. Any version lower than these three values is affected.Affected if Installed version is less than 20.14.5683.0, OR less than 20.14.4244, OR less than 20.14.2.3053 (whichever comparison applies to your version numbering scheme)
The system is affected if Intel Unison is installed and the version number is lower than 20.14.5683.0, 20.14.4244, or 20.14.2.3053, because an authenticated local user could exploit the information disclosure vulnerability to access sensitive data they are not authorized to view.
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.
From vendor data20.14.2.305320.14.424420.14.5683.0
Apply available Intel Unison software updates when released; until then, limit local access to trusted authenticated users only and follow principle of least privilege.
- 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-46646 — 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-46646 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