CWEweakness
CWE-370 Missing Check for Certificate Revocation after Initial Check
Medium
Official page ↗
- Abstraction
- Variant
- Structure
- Simple
- Status
- Draft
- Likelihood of exploit
- Medium
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
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.
Common consequences
• Access Control: Gain Privileges or Assume Identity — 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. Trust may be assigned to an entity who is not who it claims to be. 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.
• Integrity: Modify Application Data — Data from an untrusted (and possibly malicious) source may be integrated.
• Confidentiality: Read Application Data — Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.
Potential mitigations
• [Architecture and Design] Ensure that certificates are checked for revoked status before each use of a protected resource. If the certificate is checked before each access of a protected resource, the delay subject to a possible race condition becomes almost negligible and significantly reduces the risk associated with this issue.
Related
Attack pattern · CAPEC (2)
Child of · CWE (1)
- CWE-299 Improper Check for Certificate Revocation weakness
Peer of · CWE (3)
Referenced by CAPEC · weakness (2)
Referenced by CVE · weakness (1)
- CVE-2025-67108 eProsima Fast-DDS v3.3 was discovered to contain improper validation for ticket revocation, resulting in insecure communications and… vulnerability