CVE-2023-45190: IBM Engineering Lifecycle Optimization – Publishing · 644 Improper Neutralization of HTTP Headers for Scripting Syntax
Affects IBM Engineering Lifecycle Optimization – PublishingSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Engineering Lifecycle Optimization - Publishing | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should prioritize upgrading IBM Engineering Lifecycle Optimization - Publishing to versions beyond 7.0.3 once patches are released by IBM. In the interim, organizations should implement strict input validation and sanitization controls on HTTP headers at the network perimeter or application gateway level to detect and block malicious HOST header values. Web application firewalls (WAFs) can be configured with custom rules to identify and mitigate HTTP header injection attempts. Network segmentation should be enforced to limit local access to the vulnerable service, reducing the attack surface. Monitoring and logging of HTTP headers and unusual session behaviors can help detect exploitation attempts early. Additionally, organizations should review and harden cache configurations to prevent cache poisoning attacks and enforce secure session management practices to mitigate session hijacking risks. Regular security assessments and penetration testing focused on HTTP header injection vectors are recommended to validate the effectiveness of these controls.
Description
IBM Engineering Lifecycle Optimization 7.0.2 and 7.0.3 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 scripting, cache poisoning or session hijacking. IBM X-Force ID: 268754.