CVE-2022-36775
Summary
| CVE | CVE-2022-36775 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2023-02-17 17:15:00 UTC |
| Updated | 2023-11-07 03:49:00 UTC |
| Description | IBM Security Verify Access 10.0.0.0, 10.0.1.0, 10.0.2.0, 10.0.3.0, and10.0.4.0 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: 233576. |
Risk And Classification
Problem Types: CWE-74
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Ibm | Security Verify Access | 10.0.0.0 | All | All | All |
| Application | Ibm | Security Verify Access | 10.0.1.0 | All | All | All |
| Application | Ibm | Security Verify Access | 10.0.2.0 | All | All | All |
| Application | Ibm | Security Verify Access | 10.0.3.0 | All | All | All |
| Application | Ibm | Security Verify Access | 10.0.4.0 | All | All | All |
| Application | Ibm | Security Verify Access Docker | 10.0.0.0 | All | All | All |
| Application | Ibm | Security Verify Access Docker | 10.0.1.0 | All | All | All |
| Application | Ibm | Security Verify Access Docker | 10.0.2.0 | All | All | All |
| Application | Ibm | Security Verify Access Docker | 10.0.3.0 | All | All | All |
| Application | Ibm | Security Verify Access Docker | 10.0.4.0 | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| IBM X-Force Exchange | MISC | exchange.xforce.ibmcloud.com | |
| Security Bulletin: Security Vulnerabilities have been identifed in the IBM WebSphere Liberty product as shipped with the IBM Security Verify Access products. | MISC | www.ibm.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.