LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4763: IBM Sterling File Gateway 6.0.0.0 through 6.0.3.2 and 2.2.0.0 through 2.2.6.5 does not set the secure attri...

IBM Sterling File Gateway 6.0.0.0 through 6.0.3.2 and 2.2.0.0 through 2.2.6.5 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 188897.

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

Security readout for executives and security teams

Plain-English summary

IBM Sterling File Gateway versions listed by IBM failed to mark login/session cookies as secure. A user who follows or visits an HTTP link could expose those cookies over unencrypted traffic, potentially leaking access tokens. This is a confidentiality issue, not a direct remote-code-execution flaw.

Executive priority

Treat as a scheduled remediation item for managed file-transfer environments. Prioritize faster if the gateway is internet-facing, handles sensitive transfers, or users access it from shared or untrusted networks.

Technical view

CVE-2020-4763 affects IBM Sterling File Gateway 6.0.0.0 through 6.0.3.2 and 2.2.0.0 through 2.2.6.5. Authorization tokens or session cookies lack the Secure attribute, allowing browser transmission over HTTP under user-assisted conditions. CVSS v3.0 is 4.3, with network attack vector and required user interaction.

Likely exposure

Exposure is limited to organizations running the affected IBM Sterling File Gateway version ranges, especially where users can reach HTTP links or mixed HTTP/HTTPS paths while authenticated.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. Exploitation requires user interaction and access to observe insecure HTTP traffic, so risk depends on network position and application access patterns.

Researcher notes

Evidence is sufficient for affected versions, weakness class, and CVSS context. The source bundle does not provide a specific fixed version, detailed patch instructions, or confirmed exploitation. Avoid assuming broader IBM Sterling products are affected.

Mitigation direction

  • Review IBM advisory for the corrected fix level or configuration guidance.
  • Upgrade affected IBM Sterling File Gateway deployments per IBM guidance.
  • Restrict authenticated use to HTTPS-only paths wherever supported.
  • Invalidate active sessions after remediation if cookie exposure is suspected.
  • Reduce exposure to untrusted networks during the remediation window.

Validation and detection

  • Inventory IBM Sterling File Gateway versions against the affected ranges.
  • Confirm authentication cookies include the Secure attribute after remediation.
  • Verify HTTP access is redirected or blocked for authenticated workflows.
  • Review proxy and application paths for mixed HTTP handling.
  • Check IBM X-Force ID 188897 and CVE records for updates.
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-4763 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
4.3 (3.0)
Known Exploited
No
Published

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

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
4.3CVSS 3.0MediumCVSS:3.0/A:N/PR:N/I:N/C:L/AV:N/S:U/AC:L/UI:R/RC:C/RL:O/E:U2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

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

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
IBMSterling File Gateway2.2.0.0, 6.0.3.2, 2.2.6.5, 6.0.0.0Listed
Weakness

CWE details

No CWE listed

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