How severe is GHSA-8v28-3g86-chj5?

GHSA-8v28-3g86-chj5 has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8v28-3g86-chj5?

GHSA-8v28-3g86-chj5 affects the following packages: PanelSwWix4.Sdk (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-8v28-3g86-chj5?

Update PanelSwWix4.Sdk to 5.0.0-psw-wix.0251-40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v28-3g86-chj5 is resolved across your whole dependency graph.

How do I detect GHSA-8v28-3g86-chj5 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for PanelSwWix4.Sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8v28-3g86-chj5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8v28-3g86-chj5?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8v28-3g86-chj5 can be triaged on real exposure rather than presence alone.

Is GHSA-8v28-3g86-chj5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8v28-3g86-chj5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8v28-3g86-chj5 published, and has it been updated?

GHSA-8v28-3g86-chj5 was published on February 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

GHSA-8v28-3g86-chj5 — PanelSwWix4.Sdk

HIGH

GHSA-8v28-3g86-chj5 is a high-severity (CVSS 8.2) vulnerability in PanelSwWix4.Sdk. A fix is available for PanelSwWix4.Sdk — see the affected versions and patch details below.

PanelSwWix4.Sdk .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges

Published

Feb 8, 2024

Updated

Feb 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 8, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

.NETPanelSwWix4.Sdk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Summary

.be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges.

Details

If the bundle is not run as admin, the user's TEMP folder is used and not the system TEMP folder. A utility is able to monitor the user's TEMP folder for changes and drop its own DLL into the .be/.Local folder immediately when the .be folder is created. When the burn engine elevates, the malicious DLL receives elevated privileges.

PoC

As a standard, non-admin user:

Monitor the user's TEMP folder for changes using ReadDirectoryChangesW
On FILE_ACTION_ADDED, check if the folder name is .be
Create a folder in .be named after the bundle + .Local (e.g. MyInstaller.exe.Local)
Put the malicious COMCTL32.DLL in the .Local folder following the naming used for the real DLL (e.g. MyInstaller.exe.Local/x86_microsoft.windows.common-controls_.../COMCTL32.dll)
Do hacker things when the engine escalates and the malicious DLL is loaded

Proper naming for the path can be obtained by using GetModuleHandle("comctl32.dll") and GetModuleFileName.

Impact

DLL redirection utilizing .exe.Local Windows capability. This impacts any installer built with the WiX installer framework.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`PanelSwWix4.Sdk`	all versions	5.0.0-psw-wix.0251-40`dotnet add package PanelSwWix4.Sdk --version 5.0.0-psw-wix.0251-40`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for PanelSwWix4.Sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update PanelSwWix4.Sdk to 5.0.0-psw-wix.0251-40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v28-3g86-chj5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8v28-3g86-chj5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8v28-3g86-chj5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# Summary .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges. # Details If the bundle is not run as admin, the user's TEMP folder is used and not the system TEMP folder. A utility is able to monitor the user's TEMP folder for changes and drop its own DLL into the .be/.Local folder immediately when the .be folder is created. When the burn engine elevates, the malicious DLL receives elevated privileges. # PoC As a standard, non-admin user: 1. Monitor the user's TEMP folder for changes using ReadDirectoryChangesW 1. On FILE_ACTION_ADDED

O3 Security · Impact-Aware SCA

Is GHSA-8v28-3g86-chj5 in your dependencies?

O3 Security finds GHSA-8v28-3g86-chj5 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works