Skip to main content

SQ14110

Detected Windows executable files that negate ASLR by forcing predicable relocation to first granularity base.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
failhighlow3hardening: fail
Reason: unsafe code linking practices

About the issue​

Address Space Layout Randomization (ASLR) is a vulnerability mitigation option that forces software components to load on a different memory base address each time they are used. This mitigation is detected as enabled, but rendered ineffective due to highly predictable memory base assignment. When the memory base address is unspecified by being set to zero, the operating system predictably loads the image on the first memory granularity base. That completely negates the ASLR mitigation.

How to resolve the issue​

  • Review the programming language linker options.
  • In Microsoft VisualStudio, you should check if the linker option /BASE is set to zero, and change the value accordingly.

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