First published: Tue Jan 03 2023(Updated: )
IBM Security Verify Access 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.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Security Verify Access | =10.0.0.0 | |
IBM Security Verify Access | =10.0.1.0 | |
IBM Security Verify Access | =10.0.2.0 | |
IBM Security Verify Access | =10.0.3.0 | |
IBM Security Verify Access | =10.0.4.0 | |
IBM Security Verify Access Docker | =10.0.0.0 | |
IBM Security Verify Access Docker | =10.0.1.0 | |
IBM Security Verify Access Docker | =10.0.2.0 | |
IBM Security Verify Access Docker | =10.0.3.0 | |
IBM Security Verify Access Docker | =10.0.4.0 | |
IBM Security Verify Access Docker | <=10.0.X | |
IBM Security Verify Access | <=10.0.X |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-36775 refers to a vulnerability in IBM Security Verify Access that allows HTTP header injection.
CVE-2022-36775 affects IBM Security Verify Access versions 10.0.0.0, 10.0.1.0, 10.0.2.0, 10.0.3.0, and 10.0.4.0.
The severity of CVE-2022-36775 is medium with a CVSS score of 6.5.
CVE-2022-36775 could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting.
To fix the vulnerability CVE-2022-36775, apply the necessary patches provided by IBM Security Verify Access.