Unison SoftwareApplication · Intel

CVE-2022-43477

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
Incomplete cleanup 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 confidence

Intel Unison software has an incomplete cleanup vulnerability where temporary files, logs, or cached data may retain sensitive information. An authenticated user with local system access can potentially access this improperly secured data, leading to information disclosure.

MitigationApply vendor-provided patches or updates for Intel Unison when available. Until a patch is released, ensure proper access controls on system temp directories and monitor for unauthorized local access.

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

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

  1. Verify Intel Unison installation
    Search for Intel Unison in the system's installed programs list (Windows Control Panel > Programs and Features, macOS Applications folder, or Linux package manager)
    Affected if Intel Unison is not installed on the system
  2. Determine installed version
    Open Intel Unison and navigate to Help > About, or check the program's properties in the installed programs list to obtain the exact version number
    Affected if Version is 20.14.5683.0 or higher (all three branch thresholds are met)
  3. Compare against affected versions
    Check if the installed version is below any of these thresholds: 20.14.5683.0, 20.14.4244, or 20.14.2.3053
    Affected if Installed version falls below at least one of the specified version thresholds
  4. Inspect temporary data locations
    Search common temporary directories (Windows: %TEMP%, AppData\Local\Temp; macOS: /tmp, ~/Library/Caches; Linux: /tmp) for files or folders containing 'Unison' or Intel branding
    Affected if Temporary files, logs, or cached data associated with Intel Unison are found in unprotected locations

User is affected if Intel Unison version is below 20.14.5683.0 (or the other thresholds) AND temporary files, logs, or cached data from the software exist and can be accessed by local users.

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 or updates for Intel Unison when available. Until a patch is released, ensure proper access controls on system temp directories and monitor for unauthorized local access.

Recommended fix Moderate confidence

20.14.5683.0 (or later stable release)

  1. 1. Identify the current installed version of Intel Unison software
  2. 2. Navigate to the official Intel support or download page for Intel Unison software
  3. 3. Download the latest stable version of Intel Unison (version 20.14.5683.0 or later)
  4. 4. Uninstall the current version of Intel Unison software
  5. 5. Install the updated version (20.14.5683.0 or later)
  6. 6. Restart any associated services or applications if required
  7. 7. Verify the installation was successful and the version is correct
Caveat Review Intel release notes for any functionality changes between your current version and 20.14.5683.0

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

Fix this in Unison Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43477 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43477 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