CVE-2023-33855
Ibm Common Cryptographic Architecture 7.0.0 – 7.5.37
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-33855 is a low-severity Covert Timing Channel (CWE-385) vulnerability in Ibm Common Cryptographic Architecture. Its CVSS base score is 3.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Gather Victim Identity Information (T1589); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-31 (Covert Channel Analysis) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-38005
Vulnerability Data
Under certain conditions, RSA operations performed by IBM Common Cryptographic Architecture (CCA) 7.0.0 through 7.5.36 may exhibit non-constant-time behavior. This could allow a remote attacker to obtain sensitive information using a timing-based attack. IBM X-Force ID: 257676.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Covert channel analysis directly identifies timing channels that could leak information.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure development practices (reviews, testing) directly reduce introduction of timing-channel vulnerabilities in code.
Runtime monitoring of hardware/software behavior can detect anomalous timing patterns that indicate covert channels.
Vulnerability identification processes can surface timing-channel weaknesses during design or code analysis.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Training helps developers recognize timing-channel pitfalls (e.g., constant-time comparison) and avoid introducing them, but the topic is specialized enough that even a well-implemented awareness programme reaches only a minority of instances; many developers will not receive specific timing-attack training and even trained developers can miss subtle timing variations.
Continuous monitoring may detect timing-based exfiltration but does not eliminate the channel itself.
Secure coding guidelines may recommend constant-time algorithms but coverage is not guaranteed.
Security testing can uncover timing vulnerabilities but does not prevent their introduction.