WiX Burn-based bundles are vulnerable to binary hijack when run as SYSTEM

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Burn uses an unprotected C:\Windows\Temp directory to copy binaries and run them from there. This directory is not entirely protected against low privilege users. Details When a bundle runs as SYSTEM user, Burn uses GetTempPathW which points to an insecure directory C:\Windows\Temp to drop and load multiple binaries. Standard users can hijack the binary before it's loaded in the application resulting in elevation of privileges. Built in users(non-administrators) have special permissions to this folder and can create files and write to this directory. While they do not have explicit read permissions, there is a way they can monitor the changes to this directory using ReadDirectoryChangesW API and thus figure out randomized folder names created inside this directory as wel PoC PoC works against the against visual studio enterprise with update 3 installer Reproduction steps As a standard user, run the poc. Mount the iso and run visual studio installer as local system account.…

Published by the source

25 Mar 2024, 19:36 UTC

Last modified by the source

25 Mar 2024, 19:36 UTC

Source last checked

26 Oct 2026, 17:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g4v6-69p6-q3p4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-g4v6-69p6-q3p4

Advisory: WiX Burn-based bundles are vulnerable to binary hijack when run as SYSTEM
IDs: GHSA-g4v6-69p6-q3p4
Record: https://patchnext.com/advisories/ghsa-g4v6-69p6-q3p4 (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: panelswwix4.sdk 5.0.0-psw-wix.0265-49. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet panelswwix4.sdk: affected <= 5.0.0-psw-wix.0262-48; fixed in 5.0.0-psw-wix.0265-49

## Suggested inspection (read-only)
- NuGet panelswwix4.sdk: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on panelswwix4.sdk.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g4v6-69p6-q3p4 (GitHub-reviewed advisory GHSA-g4v6-69p6-q3p4 lists affected ranges: NuGet panelswwix4.sdk >=0 <=5.0.0-psw-wix.0262-48)

Commands are suggestions: review each one before running it.