dbcve.org
Unison SoftwareApplication · Intel

CVE-2022-46647

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
Insertion of sensitive information into log file 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 a vulnerability where sensitive information is being written to log files. An authenticated user with local access to the system can read these logs to disclose the sensitive data that was improperly logged.

MitigationDevelopers should review all logging statements in the Intel Unison codebase and ensure sensitive data (credentials, tokens, PII, API keys, etc.) is not written to log files, or implement proper redaction/sanitization of log output.

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 is installed
    Check for Intel Unison in installed programs (Windows: Add/Remove Programs, macOS: Applications folder, Linux: package manager list). Look for installation directory typically under C:\Program Files\Intel\Unison or /Applications/Intel Unison
    Affected if Intel Unison software is found on the system
  2. Determine installed version
    Open Intel Unison and navigate to Help > About, or check the installed version in the system registry (Windows) or application bundle info (macOS)
    Affected if Installed version is below 20.14.5683.0, 20.14.4244, or 20.14.2.3053 (note: version format varies, compare numerically)
  3. Locate log files
    Search for log files in the Intel Unison installation directory and common log locations: %LOCALAPPDATA%\Intel\Unison\Logs (Windows), ~/Library/Logs/Intel/Unison (macOS), or ~/.local/share/unison/logs (Linux)
    Affected if Log files exist in these locations
  4. Inspect logs for sensitive data
    Open each log file and search for patterns indicating sensitive information: passwords, tokens, API keys, email addresses, or other PII. Look for keywords like 'password', 'token', 'key', 'secret', 'credential' in plain text
    Affected if Log files contain any readable sensitive data such as credentials, tokens, API keys, or personal information that should not be logged

A system is affected if Intel Unison is installed with a version lower than 20.14.5683.0 (or the other cited thresholds) AND log files contain improperly logged sensitive information that could be disclosed to a local authenticated user.

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

Developers should review all logging statements in the Intel Unison codebase and ensure sensitive data (credentials, tokens, PII, API keys, etc.) is not written to log files, or implement proper redaction/sanitization of log output.

Recommended fix High confidence

20.14.5683.0 (or respective branch version: 20.14.4244 or 20.14.2.3053 or higher)

  1. 1. Identify the currently installed Intel Unison software version
  2. 2. Navigate to the Intel support or download page for Intel Unison software
  3. 3. Download the fixed version (20.14.5683.0 or higher, or 20.14.4244 or higher, or 20.14.2.3053 or higher depending on your branch)
  4. 4. Close any running instances of Intel Unison
  5. 5. Install the updated version following Intel's standard installation procedures
  6. 6. Verify the new version is correctly installed
  7. 7. Review log file configurations to ensure no sensitive information is being written

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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