SQ14153
Detected Windows executable files that opt out of dependency isolation while including a manifest that specifies how dependency loading should be performed.
| priority | CI/CD status | severity | effort | RL level | RL assessment |
|---|---|---|---|---|---|
 | pass | high | high | None | hardening: warning Reason: vulnerability mitigation issues |
About the issue
Isolated Applications and Side-by-Side Assemblies are a solution to lessen the impact of dependency version conflicts. When an application depends on a common operating system component with multiple incompatible versions, it must reference the correct one. This type of isolation provides a mechanism for versioned applications and dependencies to run simultaneously without conflicts. The operating system is informed of the correct dependency versions to load through an application manifest. It can be found within application resources or supplied as a standalone file. Using such a manifest implies that the application is isolation-aware. However, it was detected that the application was compiled to opt out of dependency isolation while also including a manifest resource. This was likely an oversight during application upgrade to include isolation capabilities.
How to resolve the issue
- In Microsoft VisualStudio, you can enable isolation by passing the option /ALLOWISOLATION to the linker.
Incidence statistics
Not relevant for this type of issue.
Recommended reading
- Isolated Applications and Side-by-side Assemblies (External resource - Microsoft)
- Application manifests (External resource - Microsoft)