LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4811: IBM Cloud Pak for Security (CP4S) 1.4.0.0, 1.5.0.0, 1.5.0.1, 1.6.0.0, and 1.6.0.1 could allow a privileged...

IBM Cloud Pak for Security (CP4S) 1.4.0.0, 1.5.0.0, 1.5.0.1, 1.6.0.0, and 1.6.0.1 could allow a privileged user to inject inject malicious data using a specially crafted HTTP request due to improper input validation.

LowCVSS 2.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity IBM Cloud Pak for Security issue where a highly privileged user could submit malformed HTTP input that changes data integrity. It is not described as a remote unauthenticated takeover. Business urgency is mainly for organizations running the listed CP4S versions with broad privileged access or weak change monitoring.

Executive priority

Handle through normal patch governance, with higher priority where CP4S is internet-accessible, supports critical security operations, or has many privileged users. This does not warrant emergency treatment based on the supplied evidence, but it should not remain unresolved indefinitely.

Technical view

Affected CP4S versions 1.4.0.0, 1.5.0.0, 1.5.0.1, 1.6.0.0, and 1.6.0.1 have improper input validation. CVSS 3.0 is 2.4: network vector, high privileges required, user interaction required, no confidentiality or availability impact, and low integrity impact.

Likely exposure

Exposure is limited to IBM Cloud Pak for Security deployments on the named versions. The CVSS vector indicates an attacker needs high privileges and user interaction, so risk is concentrated around trusted administrative users, compromised privileged accounts, or overly broad role assignments.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. IBM and X-Force describe a specially crafted HTTP request and malicious data injection, but the bundle does not provide public exploit status, exploitation scale, or detailed attack prerequisites beyond CVSS.

Researcher notes

The source bundle does not identify a CWE, affected component path, fixed version, or proof of exploitation. Validation should stay focused on version exposure, IBM advisory status, privileged-user controls, and integrity monitoring rather than exploit reproduction.

Mitigation direction

  • Check IBM advisory guidance for the official fix or upgrade path.
  • Upgrade affected CP4S deployments according to IBM-supported instructions.
  • Restrict privileged CP4S access to users with a clear operational need.
  • Review privileged account hygiene, MFA, and role assignments.
  • Monitor CP4S audit trails for unexpected privileged data changes.

Validation and detection

  • Inventory CP4S versions and identify any listed affected releases.
  • Confirm whether IBM’s advisory remediation is applied.
  • Review privileged CP4S users and remove unnecessary elevated roles.
  • Check audit logs for unusual privileged changes or malformed request patterns.
  • Document compensating controls if immediate remediation is delayed.
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-4811 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
Low
CVSS
2.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/A:N/C:N/S:U/PR:H/UI:R/I:L/AC:L/E:U/RL:O/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
2.4CVSS 3.0LowCVSS:3.0/AV:N/A:N/C:N/S:U/PR:H/UI:R/I:L/AC:L/E:U/RL:O/RC:C0.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

2.4Low
CVSS 3.0 vector shape for CVE-2020-4811Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/A:N/C:N/S:U/PR:H/UI:R/I:L/AC:L/E:U/RL:O/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
IBMCloud Pak for Security1.4.0.0, 1.6.0.0, 1.5.0.1, 1.5.0.0, 1.6.0.1Listed
Weakness

CWE details

No CWE listed

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