CVE-2023-27291
Ibm Watson Cp4D Data Stores 4.6.0 … 4.6.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/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-27291 is a medium-severity Cleartext Transmission of Sensitive Information (CWE-319) vulnerability in Ibm Watson Cp4D Data Stores. Its CVSS base score is 4.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 27th 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-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-31069
Vulnerability Data
IBM Watson CP4D Data Stores 4.6.0, 4.6.1, 4.6.2, and 4.6.3 does not encrypt sensitive or critical information before storage or transmission which could allow an attacker to obtain sensitive information. IBM X-Force ID: 248740.
- 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.
SC-8 directly requires protecting confidentiality of transmitted information, which structurally eliminates cleartext transmission of sensitive data.
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.
Encryption of data-in-transit directly prevents cleartext transmission while the control also addresses integrity and availability.
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.
A.8.24's guidance item (c) explicitly names cryptography for protection of information 'transmitted over networks', so a well-implemented clause mandates encryption of data in transit; the cleartext transmission weakness stops being present, parallel to the owner's A.8.24 removes CWE-311/CWE-312 = full rulings on the same clause text.
A.8.21 mandates identifying/implementing network service security features (explicitly including encryption and connection controls), formulating rules that cover authentication/authorization/monitoring/VPNs, and ensuring providers do the same; this stops cleartext transmission from being exploitable in the large majority of network channels, with a bounded remainder (e.g. internal non-networked flows or unaddressed legacy protocols).
Mandating cryptographic protection and stronger authentication on public networks stops the transmission of plaintext sensitive information.
A.5.17 mandates secure transmission of authentication information, removing cleartext transmission of that specific sensitive data, but does not address other sensitive information transmitted in cleartext, so it removes only a subset of CWE-319 instances.
Training helps where cleartext transmission is a developer or administrator choice (HTTP vs HTTPS, enabling secure transfer, not sending credentials in email) — the same logic that graded A.6.3 vs CWE-1428 at `mostly` — but CWE-319 is broader than CWE-1428 and includes hardware debug channels (JTAG), OT/ICS protocol choices baked into vendor products, and legacy systems where the protocol decision is not a conscious act by someone training can reach, leaving a nameable remainder that puts this below `mostly`.
A.6.7 mandates communications security requirements for remote access (items d, h, k) and the provision of suitable communication equipment with methods for securing remote access, which blocks cleartext transmission during remote working; however, CWE-319 applies to all communication channels — internal networks, server-to-server, hardware/JTAG, application-layer — and A.6.7's scope is limited to remote working, leaving the bulk of cleartext-transmission instances outside its reach.