Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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-40694 is a medium-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Ibm Watson Cp4D Data Stores. Its CVSS base score is 6.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Local Accounts (T1078.003); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-45250
Vulnerability Data
IBM Watson CP4D Data Stores 4.0.0 through 4.8.4 stores potentially sensitive information in log files that could be read by a local user. IBM X-Force ID: 264838.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Procedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.
Identifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.
Cross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.
Identifying logging as a data action allows prevention of sensitive information being inserted into log files.
The process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.
Specific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.
PIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.
Limits insertion of sensitive operational details into logs by treating such data as key information requiring protection.
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 SDLC practices directly prohibit writing sensitive data to logs; eliminating the weakness satisfies only one narrow slice of the control.
Log generation configuration can and should exclude sensitive data, but the control statement focuses on availability rather than content filtering.
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.5.15 mandates that access control rules be defined and implemented on assets including log files (it explicitly references logging under 8.15 and requires access rights and restrictions to be mapped to entities), so a well-implemented policy restricts who can read the log and blocks the exploitation; the actual enforcement, however, is performed by the access control implementation (A.8.3 and related), not by A.5.15 itself, which sits one step removed as the policy that requires the blocking to be set up.
A.8.28 mandates secure coding practices that include guidance on what not to log (sensitive data is exactly the kind of 'common and historical coding practice' the clause names), but the mechanism is human practice — developers must know what counts as sensitive, redact it, and apply that consistently across error paths and third-party libraries. This is the same practice-not-mechanism reading that graded A.8.28 -> CWE-79 and A.8.28 -> CWE-502 at `partial`, and the clause carries a declared ceiling of `partial` on this verb for code-level defects.
A.8.29's SOURCE reach (SAST, code review) catches the bulk of CWE-532 instances where sensitive data is passed directly to logging calls, and RUNTIME reach (penetration testing) can surface sensitive data in accessible logs; the remainder is bounded and nameable — cases where sensitivity is context-dependent and not flagged by configured rules, and indirect logging patterns (e.g., logging entire objects whose toString() exposes sensitive fields) that SAST rules miss.
A.8.3 restricts who may access information that exists, but CWE-532 is about the product writing sensitive information into a log file in the first place; access restriction does not stop the log entry from being created or read by an attacker who reaches the log through a different path.
A.8.30 carries secure coding practices (8.28) into outsourced work via contract, and secure coding guidance typically addresses what should not be logged, so a faithful implementation reduces instances of CWE-532 in delivered code; the ceiling is `partial` because the effect depends on the rigour of the contracted practice and the clause's own ceiling on this verb is `partial` (per the CWE-134 anchor).