dbcve.org
Unison SoftwareApplication · Intel

CVE-2022-45469

HIGH · 7.8 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 20.14.2.3053 / 20.14.4244 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper input validation for some Intel Unison software 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 confidence

Intel Unison software has improper input validation that allows an authenticated local user to escalate privileges. This is a local privilege escalation vulnerability requiring the attacker to have valid credentials and local system access.

MitigationApply vendor-provided patches for Intel Unison when available. Until then, limit local system access to trusted users and monitor for suspicious local privilege escalation activity.

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
Unison SoftwareApplication
Affected:< 20.14.5683.0< 20.14.4244< 20.14.2.3053

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Intel Unison is installed
    On Windows, open Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell. On Linux, check /opt or /usr/share for Intel Unison directories.
    Affected if Intel Unison software is present on the system
  2. Determine the installed version of Intel Unison
    Locate the Intel Unison application and check its version property. In Windows, right-click the application in Programs and Features or check the executable properties. On Linux, run 'dpkg -l | grep unison' or 'rpm -qa | grep unison'.
    Affected if The displayed version is lower than 20.14.5683.0, 20.14.4244, or 20.14.2.3053
  3. Verify the Intel Unison service or process is running
    Open Task Manager or run 'Get-Process | Where-Object {$_.ProcessName -like "*Unison*"}' in PowerShell. Also check Services.msc for Intel Unison services.
    Affected if The Intel Unison process or service is currently active on the system
  4. Confirm local user access to the system
    Review local user accounts and verify which users have authenticated access to the system. Check who can log in locally via 'query user' or examine local user group membership.
    Affected if There are authenticated local users present on the system (this is the prerequisite for the vulnerability)

A user is affected if Intel Unison is installed with a version below 20.14.5683.0 (or 20.14.4244 or 20.14.2.3053) and the software is running, allowing a local authenticated user to potentially exploit improper input validation for privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 20.14.2.3053 / 20.14.4244 / 20.14.5683.0 or later
Fixed in 20.14.2.305320.14.424420.14.5683.0
Interim mitigation

Apply vendor-provided patches for Intel Unison when available. Until then, limit local system access to trusted users and monitor for suspicious local privilege escalation activity.

Recommended fix Moderate confidence

Intel Unison version 20.14.5683.0 or later (or corresponding fixed versions in other release channels: 20.14.4244 or later, 20.14.2.3053 or later)

  1. 1. Visit the official Intel Support website and search for Intel Unison software updates
  2. 2. Download the latest version of Intel Unison (version 20.14.5683.0 or higher, or 20.14.4244 or higher, or 20.14.2.3053 or higher depending on your update channel)
  3. 3. Close any running instances of Intel Unison software
  4. 4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. 5. After installation, restart the system to ensure all components are properly updated
  6. 6. Verify the installed version matches or exceeds the fixed release version
Caveat Review Intel release notes for any compatibility changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unison Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45469 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45469 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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