LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4706: IBM API Connect 5.0.0.0 through 5.0.8.10 is vulnerable to HTTP header injection, caused by improper validat...

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.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM API Connect 5.x deployments in the listed versions may trust unvalidated Host header input. An attacker with low privileges could use crafted requests to influence how the system builds or handles HTTP responses, enabling risks such as cross-site scripting, cache poisoning, or session hijacking.

Executive priority

Treat as a moderate-priority remediation item. It is not listed as actively exploited in the provided evidence, but affected IBM API Connect systems can support security-sensitive API traffic, so externally reachable instances should be addressed ahead of routine maintenance.

Technical view

CVE-2020-4706 is an HTTP Host header injection issue in IBM API Connect 5.0.0.0 through 5.0.8.10. The CVSS 3.0 score is 5.4, network reachable, low complexity, no user interaction, low confidentiality and integrity impact, and privileges required. IBM X-Force tracks it as 187194.

Likely exposure

Exposure is limited to IBM API Connect 5.0.0.0 through 5.0.8.10. Risk is higher where affected services are reachable from untrusted networks or where shared caches, redirects, generated links, or session flows depend on incoming Host values.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. IBM describes possible outcomes including cross-site scripting, cache poisoning, and session hijacking. The CVSS vector indicates low attack complexity but privileges are required, so urgency depends on deployment exposure and access controls.

Researcher notes

Evidence is narrow but consistent: IBM API Connect 5.0.0.0 through 5.0.8.10, improper Host header validation, CVSS 5.4, IBM X-Force ID 187194. The bundle does not provide exploit proof, detailed affected components, or a specific fixed version, so validation should stay version and configuration focused.

Mitigation direction

  • Inventory IBM API Connect 5.x deployments and confirm exact versions.
  • Review IBM advisory and X-Force entry for official remediation guidance.
  • Prioritize remediation for internet-facing or partner-accessible deployments.
  • Assess edge controls for trusted Host header enforcement per vendor guidance.
  • Review cache, redirect, and session handling around affected API Connect paths.

Validation and detection

  • Confirm whether any deployment runs versions 5.0.0.0 through 5.0.8.10.
  • Check asset exposure: internet-facing, partner-facing, or internal-only.
  • Review HTTP logs for unusual Host header values or mismatched domains.
  • Verify vendor-recommended fix or configuration status is documented.
  • Confirm compensating controls do not depend on untrusted Host values.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-4706 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/I:L/S:U/UI:N/A:N/AV:N/AC:L/C:L/PR:L/RC:C/E:U/RL:O

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.0MediumCVSS:3.0/I:L/S:U/UI:N/A:N/AV:N/AC:L/C:L/PR:L/RC:C/E:U/RL:O2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.4Medium
CVSS 3.0 vector shape for CVE-2020-4706Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/I:L/S:U/UI:N/A:N/AV:N/AC:L/C:L/PR:L/RC:C/E:U/RL:O

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMAPI Connect5.0.0.0, 5.0.8.10Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.