CVE-2025-35990
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 · uneditedImproper input validation for some Intel Endpoint Management Assistant (EMA) software before version 1.14.5 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via adjacent access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
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 · high confidenceImproper input validation vulnerability in Intel Endpoint Management Assistant (EMA) user applications (Ring 3) before version 1.14.5 allows an unauthenticated, unprivileged attacker with adjacent network access to escalate privileges through low-complexity attacks requiring no user interaction or special internal knowledge.
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< 1.14.5.0CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/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.
-
Confirm Intel EMA is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software. Look for 'Intel Endpoint Management Assistant' in the results.Affected if Intel Endpoint Management Assistant appears in the installed programs list
-
Determine the installed versionIf found, note the displayed version number. Alternatively, right-click the Intel EMA executable (typically in C:\Program Files\Intel\EMA or C:\Program Files (x86)\Intel\EMA) and view Properties > Details to see the File Version.Affected if The installed version is lower than 1.14.5 (for example, 1.14.4, 1.14.0, 1.13.x, etc.)
-
Verify the service is running and network-accessibleOpen Services (services.msc) and locate the Intel EMA service. Check if it shows as Running. Also run 'netstat -an | findstr LISTENING' to see if the EMA service is listening on any TCP ports (common ports: 8080, 8443, or custom ports).Affected if The Intel EMA service is running and listening on network ports, making it accessible to adjacent network attackers
-
Confirm vulnerability applicability conditionsReview the CVE details: the flaw requires adjacent network access (local subnet), not remote internet access. The attacker must be on the same network segment as the affected system.Affected if The system is on a network where untrusted adjacent attackers could reach the Intel EMA service (for example, shared office network, untrusted VLAN)
A system is affected if Intel Endpoint Management Assistant version 1.14.4 or earlier is installed, the service is running and network-accessible, and the system is on a network where unauthenticated adjacent attackers can reach it.
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 · scoped1.14.5.0
Upgrade Intel Endpoint Management Assistant to version 1.14.5 or later to remediate the improper input validation flaw.
Intel Endpoint Management Assistant (EMA) version 1.14.5
- Obtain Intel Endpoint Management Assistant (EMA) version 1.14.5 or later from the official Intel download center or your Intel support representative
- Ensure you have appropriate administrative credentials for the Intel EMA installation
- Back up the current Intel EMA configuration and database according to your organization's backup procedures
- Stop the Intel EMA services if required by the upgrade process
- Install version 1.14.5 following Intel's standard upgrade documentation
- Verify the installation completed successfully
- Restart Intel EMA services if they were stopped
- Confirm the version number reflects 1.14.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35990 — 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-2025-35990 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