LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4195: IBM API Connect V2018.4.1.0 through 2018.4.1.10 could allow a remote attacker to hijack the clicking action...

IBM API Connect V2018.4.1.0 through 2018.4.1.10 could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions and possibly launch further attacks against the victim. IBM X-Force ID: 174859.

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

Security readout for executives and security teams

Plain-English summary

CVE-2020-4195 is a clickjacking issue in IBM API Connect 2018.4.1.0 through 2018.4.1.10. An attacker would need to trick a user into visiting a malicious website, then hijack that user's click actions. Business risk is moderate because user interaction is required, but authenticated administrative users could make the impact more meaningful.

Executive priority

Treat this as a scheduled remediation item, not an emergency, unless affected IBM API Connect consoles are used by privileged staff in high-risk browsing environments. Patch planning should be tied to API management platform maintenance and access-control review.

Technical view

IBM describes a network-accessible clickjacking vulnerability affecting API Connect V2018.4.1.0 through V2018.4.1.10. CVSS 3.0 score is 5.4 with low attack complexity, required user interaction, low confidentiality and integrity impact, and changed scope. The bundle does not name a CWE or provide detailed vendor remediation text.

Likely exposure

Exposure is limited to organizations running IBM API Connect 2018.4.1.0 through 2018.4.1.10, especially where users access management interfaces through browsers. Internet exposure is not required if an attacker can persuade an authenticated user to open malicious content.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not listed as KEV. Exploitation depends on social engineering and a victim click path, not unauthenticated direct server compromise. The stated outcome is hijacked click actions and possible follow-on attacks.

Researcher notes

Key gaps are remediation specifics and exploit observations; the provided bundle only identifies affected versions, CVSS details, and IBM references. Avoid assuming public exploit availability or a particular fixed release without consulting IBM's advisory. Validation should focus on version evidence and defensive UI framing checks.

Mitigation direction

  • Identify all IBM API Connect 2018.4.1.x deployments.
  • Check IBM advisory 6208048 for fixed versions or vendor workarounds.
  • Upgrade or remediate according to IBM's published guidance.
  • Prioritize users with administrative or privileged API Connect access.
  • Use browser and access controls to reduce exposure to untrusted content.

Validation and detection

  • Confirm installed API Connect versions are outside 2018.4.1.0 through 2018.4.1.10.
  • Review IBM X-Force ID 174859 against asset inventory.
  • Check authenticated UI pages for anti-framing protections in a controlled test.
  • Verify remediation through version evidence and change records.
Prepared
Confidence
medium
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-4195 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/A:N/AV:N/I:L/UI:R/S:C/AC:L/PR:L/C:L/RL:O/E:U/RC:C

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/A:N/AV:N/I:L/UI:R/S:C/AC:L/PR:L/C:L/RL:O/E:U/RC:C2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

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

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 Connect2018.4.1.0, 2018.4.1.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.