What is the vulnerability ID for IBM API Connect?

The vulnerability ID for IBM API Connect is CVE-2020-4706.

What is the severity of CVE-2020-4706?

The severity of CVE-2020-4706 is medium with a severity value of 5.4.

What is the affected software for CVE-2020-4706?

The affected software for CVE-2020-4706 is IBM API Connect 5.0.0.0 through 5.0.8.10.

How can the vulnerability in IBM API Connect be exploited?

The vulnerability in IBM API Connect can be exploited by sending a specially crafted HTTP request to inject HTTP HOST header.

Vulnerability/
CVE-2020-4706

medium

5.5

CWE

16/8/2021

4/8/2024

CVE-2020-4706: XSS

Q: What is the cause of the vulnerability in IBM API Connect?

The vulnerability in IBM API Connect is caused by improper validation of input by the HOST headers, leading to HTTP header injection.

First published: Mon Aug 16 2021(Updated: )

IBM API Connect 5.0.0.0 through 5.0.8.10 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. By sending a specially crafted HTTP request, a remote attacker could exploit this vulnerability to inject HTTP HOST header, which will allow the attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking. IBM X-Force ID: 187194.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM API Connect	>=5.0.0.0<=5.0.8.10
	<=V5

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

IBM-6481879

Frequently Asked Questions

What is the vulnerability ID for IBM API Connect?
The vulnerability ID for IBM API Connect is CVE-2020-4706.
What is the severity of CVE-2020-4706?
The severity of CVE-2020-4706 is medium with a severity value of 5.4.
What is the affected software for CVE-2020-4706?
The affected software for CVE-2020-4706 is IBM API Connect 5.0.0.0 through 5.0.8.10.
What is the cause of the vulnerability in IBM API Connect?
The vulnerability in IBM API Connect is caused by improper validation of input by the HOST headers, leading to HTTP header injection.
How can the vulnerability in IBM API Connect be exploited?
The vulnerability in IBM API Connect can be exploited by sending a specially crafted HTTP request to inject HTTP HOST header.

collector/nvd-index
agent/references
agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/weakness
agent/author
agent/severity
agent/softwarecombine
agent/tags
agent/description
agent/event
collector/ibm-support
source/IBM
agent/software-canonical-lookup
vendor/ibm
canonical/ibm api connect
version/ibm api connect/5.0.0.0
version/ibm api connect/5.0.8.10
canonical/ibm api connect on cloud
version/ibm api connect on cloud/v5

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.