CVE-2023-39412
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 · uneditedCross-site request forgery in some Intel Unison software may allow an authenticated user to potentially enable escalation of privilege via network 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 is a cross-site request forgery (CSRF) vulnerability in Intel Unison software. An authenticated user could be tricked into sending malicious requests that perform unintended actions, potentially leading to escalation of privilege. The attack vector is network-based, meaning it can be exploited remotely without physical 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Intel Unison is installedCheck common installation paths: Program Files\Intel\Unison or %LOCALAPPDATA%\Intel\Unison. On Windows, also check Add/Remove Programs or run: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Unison*'}. On Linux, check /opt/intel/unison or dpkg -l | grep unison.Affected if Intel Unison software is present on the system
-
Determine the installed version of Intel UnisonNavigate to the installation directory and check for version files, or right-click the Unison executable and select Properties > Details to view the File Version. Alternatively, check the Windows registry at HKLM\SOFTWARE\Intel\Unison for the Version value.Affected if The installed version is lower than 20.14.5683.0, 20.14.4244, or 20.14.2.3053 (any version below these three thresholds)
-
Verify the Intel Unison server component is runningOpen Services.msc and look for Intel Unison service, or run tasklist | findstr Unison. If it is a web-based component, check if port 4554 or 4555 is listening: netstat -an | findstr '4554|4555'.Affected if The Intel Unison service or server component is active and accepting connections
-
Confirm authentication is enabled and users are configuredCheck if local user accounts or paired mobile devices are configured in Intel Unison. Look for user configuration files in %APPDATA%\Intel\Unison or check the web interface login page accessibility.Affected if User authentication is enabled and active on the Intel Unison installation
You are affected if Intel Unison is installed with a version below 20.14.5683.0 (or the other two threshold versions), the service is running, and user authentication is active, allowing potential CSRF attacks on authenticated sessions.
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.
From vendor data20.14.2.305320.14.424420.14.5683.0
Implement anti-CSRF tokens for state-changing operations, validate Origin/Referer headers server-side, and configure SameSite cookie attributes to prevent cross-origin request forgery.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-39412 — 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-2023-39412 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