dbcve.org
Unison SoftwareApplication · Intel

CVE-2022-43666

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
Exposure of sensitive system information due to uncleared debug information 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 contains uncleared debug information (such as debug logs, debug messages, or residual debug symbols) that exposes sensitive system information to authenticated local users, potentially revealing configuration details, file paths, or other internal system data.

MitigationRemove or disable debug information from the production build of Intel Unison software, which may involve disabling debug logging, stripping debug symbols from binaries, and cleaning up any debug configuration or temporary files before deployment.

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. Identify Intel Unison installation and version
    Check the installed version of Intel Unison software on the system. On Windows, this can be found in 'Add or Remove Programs' or via the application's 'About' or 'Help' > 'Version' menu. On Linux, check the package manager or run 'unison --version' if available.
    Affected if The installed version is earlier than 20.14.5683.0, 20.14.4244, or 20.14.2.3053 (any of these three version thresholds)
  2. Locate debug log files
    Search for debug log files in common locations where Intel Unison may store logs, such as the application data directory, temp folders, or a 'logs' subfolder within the Intel Unison installation directory. Look for files with names containing 'debug' or file extensions like .log.
    Affected if Debug log files exist and contain sensitive system information such as configuration details, file paths, or internal data
  3. Inspect application configuration files
    Examine configuration files in the Intel Unison installation directory or user config directory for debug-related settings. Look for entries such as 'debug=true', 'debuglevel', 'verbose', or similar debug-enabled flags.
    Affected if Debug settings are enabled in the configuration files
  4. Check for debug symbols in binaries
    If you have access to the Intel Unison executable files, use tools like 'strings' on Linux or 'dumpbin /headers' on Windows to inspect binaries for debug symbols (look for entries like '.debug' sections or symbol strings that reveal internal function names or paths).
    Affected if Debug symbols are present in the binary files, revealing internal structure or function names

A user is affected if they are running any version of Intel Unison software earlier than 20.14.5683.0, 20.14.4244, or 20.14.2.3053 AND debug information (logs, debug-enabled settings, or debug symbols) is present in their installation.

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

Remove or disable debug information from the production build of Intel Unison software, which may involve disabling debug logging, stripping debug symbols from binaries, and cleaning up any debug configuration or temporary files before deployment.

Recommended fix Moderate confidence

Intel Unison version 20.14.5683.0 (or respective branch version 20.14.4244 or 20.14.2.3053 or later)

  1. 1. Identify the currently installed Intel Unison software version on the system
  2. 2. Navigate to the Intel Unison download page or Intel's support website
  3. 3. Download the latest version of Intel Unison (version 20.14.5683.0 or later, or the equivalent newer release for your version branch)
  4. 4. Close any running instances of Intel Unison
  5. 5. Run the installer and follow the prompts to upgrade the software
  6. 6. Verify the installed version matches or exceeds the fixed release number

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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