SQ20109
Detected digital signatures that contain a certificate revoked due to the private key compromise.
priority | CI/CD status | severity | effort | RL level | RL assessment |
---|---|---|---|---|---|
pass | high | high | None | tampering: warning Reason: revoked certificates detected |
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. Certificates have a validity period during which they can be used to create signatures. Certificates can be revoked by the certificate authority that issued them. While there can be multiple reasons for revocation, users are advised against using software applications signed with revoked certificates. This warning indicates the signing certificate was revoked due to the private key compromise. Releasing software components signed with revoked certificates may result in application errors and availability outages.
How to resolve the issueโ
- Acquire a new certificate and re-sign the software component, then publish the software package again.
Incidence statisticsโ
ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes.
For every repository, the chart shows the percentage of projects that triggered the software assurance policy. In other words, it shows how many projects were found to have the specific issue described on this page.
The percentages are calculated from the total amount of packages analyzed:
- RubyGems: 174K
- Nuget: 189K
- PyPi: 403K
- NPM: 2.1M
Recommended readingโ
- Detecting Certificate-Signed Malware (ReversingLabs blog)
- Certificate revocation (External resource - Wikipedia)