CWE-370: Missing Check for Certificate Revocation after Initial Check
The product does not check the revocation status of a certificate after its initial revocation check, which can cause the product to perform privileged actions even after the certificate is revoked at a later time.
Last updated
Overview
If the revocation status of a certificate is not checked before each action that requires privileges, the system may be subject to a race condition. If a certificate is revoked after the initial check, all subsequent actions taken with the owner of the revoked certificate will lose all benefits guaranteed by the certificate. In fact, it is almost certain that the use of a revoked certificate indicates malicious activity.
Common consequences
What can happen when CWE-370 is exploited.
Gain Privileges or Assume Identity
Affects: Access Control
Trust may be assigned to an entity who is not who it claims to be.
Modify Application Data
Affects: Integrity
Data from an untrusted (and possibly malicious) source may be integrated.
Read Application Data
Affects: Confidentiality
Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
How to prevent it
Practical mitigations for CWE-370, grouped by where in the lifecycle they apply.