Skip to main content

SQ20132

Detected digital signatures that are failing memory integrity validation check.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
failhighmedium1tampering: fail
Reason: tampered memory pages found

About the issue​

Digital signatures are applied to applications, libraries, packages, and drivers as cryptographically secured authenticity record. Signatures verify the origin and the integrity of the object they apply to. Signatures contain a cryptographic hash of the object they are signing. Windows executables may optionally be protected from tampering during runtime with page hash validation. With this integrity enforcement mechanism, any mismatch between the expected and computed hashes, on storage or in memory, is reported as a critical integrity validation failure. This can happen for a few reasons. The software package may have been damaged during network transport, or a post-signing process changed some of the package contents, or there was an attempt to tamper with the package. Discerning between these cases is impossible without manually inspecting the affected packages.

How to resolve the issue​

  • Inspect the software package for malicious software supply chain tampering.
  • If there is no evidence of tampering, re-sign and re-publish the software component.
  • If there are any post-signing processes that might modify the software package, move them to an earlier point in the release process.

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
Statistics are not collected for the SQ20132 policy at this time, or not applicable to this type of issue.