LiveActive security incident?Get immediate response
CVE Record

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

IBM Sterling File Gateway 2.2.0.0 through 2.2.6.5 and 6.0.0.0 through 6.0.3.2 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: 186280.

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 may send authorization tokens or session cookies over unencrypted HTTP because cookies lack the Secure attribute. If a user follows an HTTP link, cookie values could be exposed to traffic observers. Impact is mainly confidentiality risk, not direct system takeover in the cited record.

Executive priority

Treat as a moderate-priority remediation for environments using affected Sterling File Gateway versions. It is not reported as actively exploited, but it can expose authenticated session material if users interact with insecure HTTP paths.

Technical view

CVE-2020-4665 affects IBM Sterling File Gateway 2.2.0.0 through 2.2.6.5 and 6.0.0.0 through 6.0.3.2. The flaw is missing Secure cookie protection on authorization/session cookies. CVSS v3.0 is 4.3: network, low complexity, user interaction required, low confidentiality impact.

Likely exposure

Organizations running the affected IBM Sterling File Gateway versions are exposed, especially where users can reach the service and may follow HTTP links while authenticated. The source bundle does not identify affected configurations beyond the listed product versions.

Exploitation context

The CVE describes exposure through user interaction with an HTTP link and traffic snooping. The bundle says KEV is false and provides no cited evidence of active exploitation or public exploit use.

Researcher notes

Evidence is limited to the CVE description, IBM reference, and X-Force ID 186280. No CWE is listed in the bundle. Do not assume broader IBM Sterling products are affected without vendor confirmation.

Mitigation direction

  • Confirm whether any deployed Sterling File Gateway version is in the affected ranges.
  • Review IBM’s advisory for official remediation and supported fixed levels.
  • Apply IBM-provided fixes or configuration guidance after change control approval.
  • Reduce HTTP exposure and prefer HTTPS-only access where operationally feasible.

Validation and detection

  • Inventory Sterling File Gateway deployments and record exact product versions.
  • In an authorized test session, verify session cookies include the Secure attribute.
  • Review web access paths for unintended HTTP availability.
  • Check vendor advisory status before closing remediation tickets.
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-4665 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/AC:L/UI:R/S:U/AV:N/C:L/I:N/A:N/PR:N/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
4.3CVSS 3.0MediumCVSS:3.0/AC:L/UI:R/S:U/AV:N/C:L/I:N/A:N/PR:N/RC:C/E:U/RL:O2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/AC:L/UI:R/S:U/AV:N/C:L/I:N/A:N/PR:N/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
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.