LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38997: IBM API Connect HOST header injection

IBM API Connect V10.0.0.0 through V10.0.5.0, V10.0.1.0 through V10.0.1.7, and V2018.4.1.0 through 2018.4.1.19 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: 213212.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM API Connect has a Host header validation flaw in listed 10.x and 2018.4.1.x releases. A logged-in network attacker could influence how the system handles Host headers, potentially enabling cross-site scripting, cache poisoning, or session hijacking. Treat this as moderate business risk for exposed API management environments.

Executive priority

Prioritize remediation for internet-facing or partner-facing API Connect environments. The issue is not rated critical and active exploitation is not evidenced here, but session hijacking and cache poisoning outcomes can create meaningful business impact if the platform is exposed.

Technical view

CVE-2021-38997 is HTTP header injection in IBM API Connect due to improper Host header input validation. The CVSS 3.1 score is 5.4 with network access, low complexity, low privileges, no user interaction, and limited confidentiality and integrity impact. Sources map it to CWE-644 and IBM X-Force ID 213212.

Likely exposure

Exposure is limited to IBM API Connect V10.0.0.0 through V10.0.5.0, V10.0.1.0 through V10.0.1.7, and V2018.4.1.0 through 2018.4.1.19. Systems not running those releases are not identified as affected in the supplied sources.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The CVSS vector requires low privileges, so risk is higher where untrusted or broadly provisioned users can reach affected API Connect interfaces.

Researcher notes

Evidence is constrained to the CVE description, IBM advisory reference, and X-Force entry reference. The bundle does not provide fixed version numbers, proof-of-concept details, or exploit telemetry. Avoid assuming exploitability beyond the stated low-privilege Host header injection condition.

Mitigation direction

  • Inventory IBM API Connect deployments and record exact release versions.
  • Review IBM advisory node 6842621 for supported fixes or interim guidance.
  • Upgrade or remediate affected instances using IBM-supported instructions.
  • Limit access to affected interfaces while remediation is pending, where feasible.

Validation and detection

  • Compare deployed versions against the affected ranges in the CVE record.
  • Confirm remediation status against IBM advisory and X-Force ID 213212.
  • Review edge caches and proxies for suspicious Host header anomalies.
  • Verify public and internal exposure paths to API Connect interfaces.
Prepared
Confidence
high
Sources
4

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.

cwe · low confidence lookup

CWE-644: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-38997 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.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2021-38997Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 Connect10.0.0.0, 10.0.1.0, 2018.4.1.0unaffected
Weakness

CWE details

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

CWE-644 · source CWE mapping

Improper Neutralization of HTTP Headers for Scripting Syntax

Improper Neutralization of HTTP Headers for Scripting Syntax represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.