Skip to main content

SQ14117

Detected Windows executable files that might not cover the entire application with buffer overrun vulnerability mitigation.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
passlowlowNonehardening: warning
Reason: ineffective mitigations detected

About the issue​

Buffer overrun protection (Stack Guard) is a vulnerability mitigation option that prevents stack-based memory corruptions. This mitigation is detected as enabled, but the application reports zero surface coverage in its internal data structures. Based on the self-reported data, it is probable that the vulnerability mitigation option has not been enabled. Modern applications usually have some functions that need to be protected against buffer overflows. Therefore, it is likely that protection coverage gaps exist.

How to resolve the issue​

  • In Microsoft VisualStudio, you can enable buffer overrun protection mitigation by setting the linker option /GS to ON.
  • If the issue persists, you should review the linker options in any static libraries that the application links with.

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).