LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4914: IBM Cloud Pak System Software Suite session fixation

IBM Cloud Pak System Suite 2.3.3.0 through 2.3.3.5 does not invalidate session after logout which could allow a local user to impersonate another user on the system. IBM X-Force ID: 191290.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Cloud Pak System Software Suite could leave a logged-out session usable. A local user with some access could potentially reuse that session to act as another user. The business risk is unauthorized changes or actions in affected IBM Cloud Pak System environments, not remote internet-scale compromise based on the provided sources.

Executive priority

Treat this as a targeted operational integrity risk. It is not described as remotely exploitable or actively exploited, but affected shared or administrator-accessible systems should be remediated promptly because impersonation can undermine trust in privileged actions.

Technical view

CVE-2020-4914 is a CWE-613 session lifecycle flaw in IBM Cloud Pak System Software Suite 2.3.3.0 through 2.3.3.5. Logout does not invalidate the session, enabling local, low-privileged impersonation with high integrity impact. CVSS 3.1 is 5.5 with vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N.

Likely exposure

Exposure is likely limited to organizations running IBM Cloud Pak System Software Suite 2.3.3.0 through 2.3.3.5, especially where multiple local users can access the same system context or administrative interface. The source bundle does not identify other affected IBM products.

Exploitation context

The source bundle does not indicate CISA KEV listing or active exploitation. Exploitation is characterized as local, low-complexity, and requiring existing low privileges. The plausible impact is session-based impersonation after logout, affecting integrity rather than confidentiality or availability per the CVSS vector.

Researcher notes

The provided evidence names session non-invalidation after logout and local impersonation, but does not include detailed exploit mechanics or a specific fixed build in the bundle. Avoid expanding scope beyond IBM Cloud Pak System Software Suite 2.3.3.0 through 2.3.3.5 without vendor confirmation.

Mitigation direction

  • Identify all IBM Cloud Pak System Software Suite deployments and versions.
  • Check IBM advisory for the vendor-supported fixed level or remediation guidance.
  • Prioritize remediation for shared administration hosts or multi-user operational environments.
  • Restrict local access to affected systems until remediation is complete.
  • Review session timeout and logout controls if configurable.

Validation and detection

  • Confirm whether installed versions fall within 2.3.3.0 through 2.3.3.5.
  • Verify remediation status against IBM advisory and X-Force entry.
  • Review audit logs for unusual actions after user logout events.
  • Test logout behavior in a controlled, authorized environment without weaponizing reuse.
  • Document compensating access restrictions while awaiting vendor remediation.
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-613: 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-2020-4914 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2020-4914Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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
IBMCloud Pak System Software Suite2.3.3.0unaffected
Weakness

CWE details

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

CWE-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.