Skip to main content

SQ20124

Detected digital signatures that contain a certificate with a short and predictable serial number.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
NonepasslowmediumNoneNone

About the issue​

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures are made using digital certificates, which can either be purchased from certificate authorities or be self-issued. When purchased from a certificate authority, a certificate must conform to industry standards and best practices. One such requirement is that certificate serial numbers should not be a short or a sequential integer. Every certificate authority must generate a unique serial number on each issuance. That number should not be predictable, as attackers may leverage this to create forged certificates with identical or similar attributes. While a commercial certificate authority is unlikely to go against these recommendations, some policy deviations can occur in practice.

How to resolve the issue​

  • Communicate the detected issue to your certificate issuer, and have a new certificate created to resolve it.
  • Re-sign the software component with your newly issued certificate.

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