Skip to main content

SQ18110

Detected Linux executable files that might ineffectively generate the security cookie value, making the buffer overrun vulnerability mitigation protection less effective.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
passmediummediumNonehardening: warning
Reason: reduced effectiveness mitigations

About the issue​

The stack canary is a special value written onto the stack that allows the operating system to detect and terminate the program if a stack overrun occurs. The user can override the stack canary implementation, which makes it possible for the attacker to reconstruct the canary and render the mitigation ineffective.

How to resolve the issue​

  • Good practice is to leave the stack canary implementation to the compiler, since modern compilers will take adequate measures to prevent the stack cookie from being trivially determined.

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