LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1546: IBM API Connect information disclosure

IBM API Connect 5.0.0.0 through 5.0.8.3 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-Force ID: 142650.

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

Security readout for executives and security teams

Plain-English summary

IBM API Connect 5.0.0.0 through 5.0.8.3 may fail to properly enable HSTS. That can leave users exposed to man-in-the-middle interception, where sensitive information could be observed if network traffic is downgraded or intercepted.

Executive priority

Treat as a targeted confidentiality risk, not a broad emergency. Prioritize environments handling sensitive API management data, internet-facing portals, or administrator access from untrusted networks.

Technical view

CVE-2018-1546 is an information disclosure issue in IBM API Connect caused by improper HTTP Strict Transport Security enablement. The CVSS 3.1 score is 5.9, with network attack vector, high attack complexity, no privileges, no user interaction, and high confidentiality impact.

Likely exposure

Exposure is limited to IBM API Connect 5.x deployments in the listed affected versions, especially where users access services over untrusted networks or through misconfigured TLS/HSTS paths.

Exploitation context

The provided sources support man-in-the-middle information disclosure risk, not confirmed active exploitation. CISA KEV status is false in the bundle, and no exploit evidence is provided.

Researcher notes

The source bundle identifies the flaw, affected range, CVSS vector, and MITM-based disclosure scenario. It does not provide patch-level detail, exploit evidence, or alternate mitigations, so remediation should be tied to IBM guidance.

Mitigation direction

  • Inventory IBM API Connect deployments and identify any 5.0.0.0 through 5.0.8.3 instances.
  • Review IBM advisory and X-Force entry for fixed versions or vendor-approved workarounds.
  • Apply IBM-recommended updates or configuration changes where available.
  • Verify HSTS is enabled consistently on exposed API Connect web endpoints.
  • Review TLS termination, proxies, and load balancers for header stripping or downgrade behavior.

Validation and detection

  • Confirm deployed IBM API Connect version against the affected version list.
  • Check exposed HTTPS responses for a valid Strict-Transport-Security header.
  • Validate HSTS behavior through all reverse proxies and TLS termination points.
  • Review network architecture for user paths crossing untrusted networks.
  • Document whether IBM advisory remediation has been applied.
Prepared
Confidence
medium
Sources
5

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-2018-1546 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.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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
4Source 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.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2018-1546Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 Connect5.0.1.0, 5.0.0.0, 5.0.2.0, 5.0.5.0, 5.0.6.0, 5.0.6.1, 5.0.6.2, 5.0.7.0, 5.0.7.1, 5.0.3.0, 5.0.4.0, 5.0.7.2, 5.0.6.3, 5.0.6.4, 5.0.8.0, 5.0.8.1, 5.0.6.5, 5.0.6.6, 5.0.8.2, 5.0.8.3unaffected
Weakness

CWE details

No CWE listed

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