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-23474 is a low-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Ibm Cognos Controller. Its CVSS base score is 3.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Domain Accounts (T1078.002); ranked at the 38th 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 SI-11 (Error Handling) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-27574
Vulnerability Data
IBM Cognos Controller 10.4.1, 10.4.2, and 11.0.0 could allow a remote attacker to obtain sensitive information when a stack trace is returned in the browser. IBM X-Force ID: 245403.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V16.5.1
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
si-11 directly requires error messages to avoid revealing exploitable information about the system or its 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.
Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.
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.
Security testing can detect error messages that leak sensitive information.
Training makes developers aware that error messages must not leak sensitive information and that exception output should be sanitized, which prevents a minority of instances; the remainder is the same fallible-developer problem that caps A.8.28 against code-level defects like XSS.
Secure coding standards explicitly forbid exposing sensitive data in errors.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-209 is a regular software CWE that secure coding addresses, but the clause's reach depends on supplier implementation and error-message hygiene is one slice of what secure coding covers, with externally-generated error messages outside the developer's direct control.
A.8.5 guidance items (a) and (c) specifically address error messages during the log-on procedure — not displaying sensitive information until log-on completes, and not providing help messages that would aid an unauthorized user (e.g., not indicating which part of the data is correct or incorrect). This removes a narrow subset of CWE-209 (log-on error message leaks), but the vast majority of CWE-209 instances — database errors, file processing errors, configuration errors, and general application error handling — are outside A.8.5's scope.
A.8.9's templates and configuration enforcement can remove configuration-level instances of CWE-209 (e.g., disabling verbose error pages, suppressing debug output, setting generic error responses), but cannot reach the majority of instances where application code explicitly constructs error messages containing sensitive data — those require code changes the clause does not perform.