Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
CWE-370 Variant Draft
Missing Check for Certificate Revocation after Initial Check
This vulnerability occurs when software only verifies a certificate's revocation status once, then continues to trust it for subsequent privileged actions without re-checking. This allows operations…
Definition
What is CWE-370?
This vulnerability occurs when software only verifies a certificate's revocation status once, then continues to trust it for subsequent privileged actions without re-checking. This allows operations to proceed even if the certificate is revoked later.
A single initial revocation check creates a dangerous race condition. If an attacker's certificate is revoked after that first check, the system will continue granting it full privileges for all later requests, as if the certificate were still valid. This essentially nullifies the security guarantee that revocation provides.
Since certificate revocation almost always signals a compromise or malicious intent, failing to re-validate before each privileged action is a critical oversight. To prevent this, your code must perform a fresh revocation check (e.g., via OCSP or CRL) every time the certificate is used to authorize a sensitive operation, not just during the initial handshake or connection setup.
Real-world impact
Real-world CVEs caused by CWE-370
No public CVE references are linked to this CWE in MITRE's catalog yet.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 4
Iterate until the response leaks data, executes attacker code, or escalates privileges.
Vulnerable code example
Vulnerable C
The following code checks a certificate before performing an action.
if (cert = SSL_get_peer_certificate(ssl)) {
foo=SSL_get_verify_result(ssl);
if (X509_V_OK==foo)
```
//do stuff*
foo=SSL_get_verify_result(ssl);
*//do more stuff without the check.* Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-370
- 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.
Detection signals
How to detect CWE-370
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
Plexicus auto-detects CWE-370 and opens a fix PR in under 60 seconds.
Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.
Frequently asked questions What is CWE-370?
How serious is CWE-370?
What languages or platforms are affected by CWE-370?
How can I prevent CWE-370?
How does Plexicus detect and fix CWE-370?
Where can I learn more about CWE-370?
Frequently asked questions
What is CWE-370?
This vulnerability occurs when software only verifies a certificate's revocation status once, then continues to trust it for subsequent privileged actions without re-checking. This allows operations to proceed even if the certificate is revoked later.
How serious is CWE-370?
MITRE rates the likelihood of exploit as Medium — exploitation is realistic but typically requires specific conditions.
What languages or platforms are affected by CWE-370?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-370?
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.
How does Plexicus detect and fix CWE-370?
Plexicus's SAST engine matches the data-flow signature for CWE-370 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-370?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/370.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-370
CWE-299 Parent
Improper Check for Certificate Revocation
This vulnerability occurs when an application fails to properly verify whether a security certificate has been revoked, potentially…
CWE-296 Peer
Improper Following of a Certificate's Chain of Trust
This vulnerability occurs when software fails to properly validate the entire certificate chain back to a trusted root authority. This…
CWE-297 Peer
Improper Validation of Certificate with Host Mismatch
This vulnerability occurs when an application accepts a valid SSL/TLS certificate without properly verifying that it actually belongs to…
CWE-298 Peer
Improper Validation of Certificate Expiration
This vulnerability occurs when an application fails to properly check if a digital certificate has expired, potentially trusting…
Ready when you are
Don't Let Security
Weigh You Down.
Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.