CWE · MITRE source
CWE-385Covert Timing Channel
Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system behavior and infer protected information.
In some instances, knowing when data is transmitted between parties can provide a malicious user with privileged information. Also, externally monitoring the timing of operations can potentially reveal sensitive data. For example, a cryptographic operation can expose its internal state if the time it takes to perform the operation varies, based on the state. Covert channels are frequently classified as either storage or timing channels. Some examples of covert timing channels are the system's paging rate, the time a certain transaction requires to execute, and the time it takes to gain access to a shared bus.
Last updated: 04 July 2026 08:17 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 2 framework(s): CAPEC 1 (partial) · ATT&CK 1 (partial)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-31 | Covert Channel Analysis | SC | Directly targets covert timing channels by requiring identification and bandwidth estimation, enabling mitigation that reduces or eliminates their usability. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-53826 UPD | 7.0 | 9.8 | 0.0050 | 2025-07-15 |
CVE-2019-3732 | 5.5 | 7.5 | 0.0141 | 2019-09-30 |
CVE-2020-25658 | 5.5 | 7.5 | 0.0163 | 2020-11-12 |
CVE-2023-3640 UPD | 5.5 | 7.0 | 0.0072 | 2023-07-24 |
CVE-2024-23342 UPD | 5.5 | 7.4 | 0.0098 | 2024-01-23 |
CVE-2023-46809 | 5.5 | 7.4 | 0.0130 | 2024-09-07 |
CVE-2025-0306 UPD | 5.5 | 7.4 | 0.0063 | 2025-01-09 |
CVE-2025-59425 | 5.5 | 7.5 | 0.0053 | 2025-10-07 |
CVE-2026-5598 UPD | 5.5 | 7.5 | 0.0069 | 2026-04-15 |
CVE-2017-2624 | 3.5 | 5.9 | 0.0067 | 2018-07-27 |
CVE-2018-10844 | 3.5 | 5.9 | 0.0362 | 2018-08-22 |
CVE-2018-10845 | 3.5 | 5.9 | 0.0362 | 2018-08-22 |
CVE-2018-10846 | 3.5 | 5.6 | 0.0039 | 2018-08-22 |
CVE-2016-7056 | 3.5 | 5.5 | 0.0059 | 2018-09-10 |
CVE-2019-19338 | 3.5 | 5.5 | 0.0046 | 2020-07-13 |
CVE-2020-25659 | 3.5 | 5.9 | 0.0245 | 2021-01-11 |
CVE-2020-25657 | 3.5 | 5.9 | 0.0173 | 2021-01-12 |
CVE-2022-24409 | 3.5 | 5.9 | 0.0109 | 2022-02-23 |
CVE-2020-29506 | 3.5 | 6.8 | 0.0097 | 2022-07-11 |
CVE-2020-35164 | 3.5 | 6.7 | 0.0067 | 2022-07-11 |
CVE-2020-35166 | 3.5 | 5.1 | 0.0062 | 2022-07-11 |
CVE-2023-49092 | 3.5 | 5.9 | 0.0060 | 2023-11-28 |
CVE-2024-23170 UPD | 3.5 | 5.5 | 0.0031 | 2024-01-31 |
CVE-2024-2236 UPD | 3.5 | 5.9 | 0.0111 | 2024-03-06 |
CVE-2024-25964 UPD | 3.5 | 5.3 | 0.0067 | 2024-03-25 |