LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4284: IBM Cloud Private 2.1.0 , 3.1.0, 3.1.1, and 3.1.2 could allow a local privileged user to obtain sensitive O...

IBM Cloud Private 2.1.0 , 3.1.0, 3.1.1, and 3.1.2 could allow a local privileged user to obtain sensitive OIDC token that is printed to log files, which could be used to log in to the system as another user. IBM X-Force ID: 160512.

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

Security readout for executives and security teams

Plain-English summary

IBM Cloud Private versions 2.1.0, 3.1.0, 3.1.1, and 3.1.2 may write sensitive OIDC tokens into log files. A local privileged user could use those tokens to log in as another user. This is not a remote, unauthenticated issue, but it can undermine user accountability and confidentiality inside affected environments.

Executive priority

Treat as a targeted internal exposure issue, not an internet-wide emergency. Prioritize affected production or shared administrative environments because leaked tokens can bypass normal user identity boundaries and complicate incident accountability.

Technical view

CVE-2019-4284 is an information disclosure issue in IBM Cloud Private where sensitive OIDC tokens are printed to logs. The CVSS 3.0 score is 4.4 with local attack vector, high privileges required, low complexity, and high confidentiality impact. IBM X-Force tracks it as ID 160512.

Likely exposure

Exposure is limited to IBM Cloud Private 2.1.0, 3.1.0, 3.1.1, and 3.1.2 deployments. The attacker must already be a local privileged user with access to relevant logs, so risk is highest in shared administration, operations, or compromised privileged-account scenarios.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The practical concern is insider misuse or post-compromise privilege abuse: a privileged local user reviews logs, obtains an OIDC token, and may impersonate another user.

Researcher notes

Evidence supports affected versions, local privileged prerequisites, token disclosure in logs, and possible login as another user. The bundle does not include detailed IBM fix instructions, exploit details, affected configurations beyond listed versions, or evidence of exploitation in the wild.

Mitigation direction

  • Apply IBM advisory remediation for affected IBM Cloud Private versions.
  • Restrict log file access to required administrators only.
  • Review log retention and handling for exposed authentication tokens.
  • Invalidate or rotate potentially exposed OIDC sessions after remediation.
  • Monitor authentication logs for unusual user impersonation patterns.

Validation and detection

  • Inventory IBM Cloud Private versions across all environments.
  • Confirm whether versions 2.1.0, 3.1.0, 3.1.1, or 3.1.2 are present.
  • Review relevant logs for accidental OIDC token exposure.
  • Verify IBM remediation is applied and token logging no longer occurs.
  • Check privileged local user access to log locations.
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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-4284 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.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/UI:N/A:N/C:H/I:N/AC:L/S:U/AV:L/PR:H/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.4CVSS 3.0MediumCVSS:3.0/UI:N/A:N/C:H/I:N/AC:L/S:U/AV:L/PR:H/RC:C/RL:O/E:U0.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.4Medium
CVSS 3.0 vector shape for CVE-2019-4284Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/UI:N/A:N/C:H/I:N/AC:L/S:U/AV:L/PR:H/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
IBMCloud Private2.1.0, 3.1.0, 3.1.1, 3.1.2Listed
Weakness

CWE details

No CWE listed

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