Skip to main content

SQ14161

Detected Windows executable files that are not using a cryptographically secure GUID for their PDB identifier.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
passlowlowNoneNone

About the issue​

Program database (PDB) files are typically only used during software development. They contain private debug symbols that make it significantly easier to determine the root cause of a software quality issue. Applications built to support debugging link to their program databases through Globally Unique Identifiers (GUIDs). This sequence of pseudo-random numbers is guaranteed to be uniquely generated. As this is the main verification that the correct debugging symbols have been loaded, it is important that the identifier has been generated securely. Using non-cryptographically secure algorithms for their generation increases the odds of identifier collisions.

How to resolve the issue​

  • Since some programming language toolchains use unsafe GUIDs, you should maintain a list of trusted debugging servers for the development environment.

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