CVE-2023-47143
Ibm Tivoli Application Dependency Discovery Manager 7.3.0.0 – 7.3.0.11
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2023-47143 is a critical-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Ibm Tivoli Application Dependency Discovery Manager. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-51278
Vulnerability Data
IBM Tivoli Application Dependency Discovery Manager 7.3.0.0 through 7.3.0.10 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site…
more
scripting, cache poisoning or session hijacking. IBM X-Force ID: 270270.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.2.1V1.2.3V4.2.3
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly requires checking/neutralizing untrusted data such as HTTP headers before they reach browser components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper output encoding and header sanitization to prevent scripting injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.
Security testing catches header-injection issues before release, covering most of the weakness.
Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.
Application security requirements explicitly call for neutralizing untrusted data in HTTP headers.
Secure architecture principles reduce injection surfaces but do not prescribe header-specific controls.