Skip to main content

SQ14152

Detected Windows executable files that do not require dependency isolation.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
passlowhighNonehardening: warning
Reason: dependency isolation problems

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. Modern applications (and their dependencies) should always be isolation-aware. When a dependency is isolated, the operating system becomes responsible for its context activation, and it ensures the environment of the hosting application is not perturbed. Disabling isolation makes components responsible for their own context activation, which may lead to incorrect software behaviors, runtime issues, and unexpected crashes.

How to resolve the issue​

  • In Microsoft VisualStudio, you can enable isolation by passing the option /ALLOWISOLATION to the linker.

Incidence statistics​

ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes. Analysis results are used to calculate incidence statistics for issues (policy violations) that Spectra Assure can detect in software packages.

This section is updated when new data becomes available.

Total amount of packages analyzed

  • RubyGems: 183K
  • Nuget: 644K
  • PyPi: 628K
  • NPM: 3.72M

Total detections per repository

For every repository, the chart shows the number of packages that triggered the software assurance policy. In other words, it shows how many packages in each package repository were found to have the specific issue described on this page. This information helps you understand how common the issue is across different software communities.

If a repository is absent from the chart, that means none of the packages in that repository triggered this policy during analysis, or the policy was not used during analysis.

Distribution of total detections by project popularity

For every repository, the chart shows how many of the total detections belong to the Top 100 (1-100), Top 1000 (101-1000) and Top 10 000 (1001-10 000) most downloaded projects. This information helps you understand the impact of the issue within each community, making it clearer when the issue affects the most popular projects.

If the chart shows zero values for all of the top project groups, that means all detections were in unranked projects (lower than 10 000 on the list of most downloaded projects).