CVE-2022-34306 json
IBM CICS TX Standard and Advanced 11.1 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers.
published 4y ago modified 4mo ago also EUVD-2022-37262
- cvss
- 5.4
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
IBM CICS TX Standard and Advanced 11.1 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: 229435.
Patch / fix
- ibm.com/support/pages/node/6601663 advisory
- ibm.com/support/pages/node/6601659 advisory
Is CVE-2022-34306 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.4 | CVSS:3.0/AC:L/C:L/I:L/A:N/UI:N/PR:L/S:U/AV:N/RC:C/RL:O/E:U |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:P/A:N |
Affected products
- IBM CICS TX Advanced
- IBM CICS TX Standard
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
ibm.com
/support/pages/node/6601663
patch, vendor-advisory
-
ibm.com
/support/pages/node/6601659
patch, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/229435
vdb-entry, vendor-advisory
Sources
- CVE List CVE-2022-34306
- NVD CVE-2022-34306
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.