CVE-2022-46299
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 · uneditedInsufficient control flow management 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 confidenceThis vulnerability in Intel Unison software involves insufficient control flow management that allows an authenticated user with local access to potentially disclose sensitive information. The issue stems from improper handling of control flow within the application, which could enable unauthorized data 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< 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 is installedCheck installed programs via Windows Settings > Apps > Installed apps, or look for Intel Unison in the program menu or Program Files directoryAffected if Intel Unison is present on the system
-
Identify the installed versionRight-click the Intel Unison executable (typically in Program Files or Program Files (x86)), select Properties, and view the File Version on the Details tab. Alternatively, check Add/Remove Programs for the version entry.Affected if A version number is displayed that can be compared to the thresholds
-
Compare version against affected rangesCheck if the installed version is less than 20.14.5683.0, or less than 20.14.4244, or less than 20.14.2.3053. Note that version comparison should account for the full version string format.Affected if The installed version falls below any of these three thresholds
-
Assess local access exposureDetermine whether the system allows or could allow local (physical or terminal) access by users other than the intended administrator. Check for shared workstations, terminal services, or physical security controls.Affected if Non-admin or untrusted users have or could gain local access to the machine running Intel Unison
-
Check authentication configurationReview Intel Unison user accounts and authentication settings to confirm which local users can log into the application. Verify if guest or limited accounts have access.Affected if Local users other than administrators can authenticate to Intel Unison
The system 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 non-admin users can authenticate to the application from local access.
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.
dbcve · scoped20.14.2.305320.14.424420.14.5683.0
Apply the latest Intel Unison software update or patch provided by Intel to address the insufficient control flow management. Verify that local access controls and authentication mechanisms are properly configured as per vendor hardening guidelines.
Intel Unison version 20.14.5683.0 (or 20.14.4244 / 20.14.2.3053 depending on your release branch)
- Identify the currently installed Intel Unison software version on the affected system
- Determine which of the three version branches (20.14.5683.0, 20.14.4244, or 20.14.2.3053) applies to your installation
- Download Intel Unison software version 20.14.5683.0 or later from the official Intel support website
- Backup any critical data or configurations before upgrading
- Close any running instances of Intel Unison software
- Run the installer for the upgraded version and follow the on-screen prompts
- Restart the system if required by the installer
- Verify the installed version matches or exceeds the fixed release (20.14.5683.0 or respective branch minimum)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46299 — 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-46299 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