Safeguard
Vulnerability Analysis•

CVE-2023-28739: Medium Default Permissions Flaw in Intel Chipset Driver

CVE-2023-28739 is an incorrect default permissions flaw in Intel Chipset Device Software. Update to 10.1.19444.8378 or later; Intel rates it Medium.

Safeguard Security Team
3 min read

CVE-2023-28739 is an incorrect default permissions flaw in Intel Chipset Device Software that may allow privilege escalation through local access. NVD and Intel score it 6.7, Medium. All versions before 10.1.19444.8378 are affected, and Intel recommends updating to that version or later.

What's affected

Intel advisory INTEL-SA-00928 lists Intel Chipset Device Software before version 10.1.19444.8378 as affected, with that version as the fix. Intel's vector is CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H, scoring 6.7. NVD agrees, so there is no severity conflict.

This software is installed on a very large number of Windows PCs with Intel chipsets, because it provides the INF files that tell Windows how to identify chipset components.

How to check if you're exposed

In Windows, open Device Manager or Apps and features and look for Intel Chipset Device Software and its version. To list it from PowerShell:

Get-CimInstance Win32_Product -Filter "Name like 'Intel(R) Chipset%'" | Select-Object Name, Version

If the software is absent, the machine may still use chipset drivers from Windows Update, so confirm with your endpoint management tool.

What to do now

  1. Install Intel Chipset Device Software 10.1.19444.8378 or later from Intel's download page.
  2. Push the update through your endpoint management tool and report on the installed versions.
  3. Limit local logon rights, since the attack needs local access and some user interaction.
  4. Check for other vendor driver updates released alongside it.
  5. Keep a note of the version in your asset list so the next audit can confirm it quickly.
  6. Check the Gold page for this CVE for later changes.

Why it matters

The weakness class is CWE-276 (Incorrect Default Permissions). A file or folder installed by the software has permissions that are wider than they should be. A low-privileged local user may be able to change something that a higher-privileged process later relies on.

The usual result of this class is privilege escalation. It needs local access, user interaction and high complexity, so it is mostly useful after an attacker already has a foothold on the machine. Clearing it is still cheap, because Intel ships the fix as a small software update.

Chipset and driver packages are the kind of software that never gets a reminder. They install at imaging time and then stay put for years. Add them to the same patch reports as the operating system, with version targets drawn from vendor advisories like this one. A quarterly report of installed chipset software versions, grouped by model, is enough to find the machines that were imaged long ago and never touched again.

Quick check

Is a reboot needed?

Intel's advisory does not say. Follow the installer's prompts and your change process.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.