LiveActive security incident?Get immediate response
CVE Record

CVE-2021-20539: IBM Cloud Pak for Security (CP4S) 1.5.0.0, 1.5.1.0, 1.6.0.0, 1.6.1.0, 1.7.0.0, and 1.7.1.0 could disclose s...

IBM Cloud Pak for Security (CP4S) 1.5.0.0, 1.5.1.0, 1.6.0.0, 1.6.1.0, 1.7.0.0, and 1.7.1.0 could disclose sensitive information to an unauthorized user through HTTP GET requests. This information could be used in further attacks against the system. IBM X-Force ID: 198920.

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

Security readout for executives and security teams

Plain-English summary

IBM Cloud Pak for Security had an information disclosure issue where unauthenticated HTTP GET requests could reveal sensitive data. The disclosed information could help an attacker plan follow-on attacks. The business risk is moderate unless an affected CP4S instance is internet-exposed or contains high-value operational security data.

Executive priority

Treat as a moderate-priority remediation item. Prioritize quickly if CP4S is externally reachable, contains sensitive security telemetry, or supports incident response workflows. Otherwise handle through normal vulnerability management with vendor-confirmed remediation.

Technical view

CVE-2021-20539 affects IBM Cloud Pak for Security versions listed in the CVE source bundle. CVSS 3.0 score is 5.3 with network attack vector, low complexity, no privileges, and no user interaction. Impact is limited to confidentiality; integrity and availability are not affected by the CVSS vector.

Likely exposure

Exposure is most likely where IBM Cloud Pak for Security deployments match the affected 1.5.x, 1.6.x, or 1.7.x versions and are reachable by unauthorized users over HTTP. The source bundle has version-list inconsistencies, so verify against IBM advisory data.

Exploitation context

The CVE is not listed as KEV in the provided bundle. CVSS marks exploit maturity as unproven. Sources support unauthenticated network reachability, but they do not provide evidence of active exploitation.

Researcher notes

Public details are limited. No CWE is listed in the bundle. The core issue is sensitive information disclosure through HTTP GET requests. The affected version list differs between source fields, so researchers should rely on IBM’s advisory for final affected-version confirmation.

Mitigation direction

  • Review IBM advisory and X-Force entry for official remediation guidance.
  • Confirm the exact installed CP4S version before deciding exposure.
  • Upgrade or apply vendor-provided fixes where IBM identifies a corrected release.
  • Restrict unauthenticated network access to CP4S management surfaces where possible.
  • Monitor HTTP request logs for suspicious unauthenticated GET activity.

Validation and detection

  • Inventory all IBM Cloud Pak for Security deployments and versions.
  • Compare installed versions with the affected versions in IBM and CVE sources.
  • Check whether CP4S endpoints are reachable by unauthorized users.
  • Review access logs for unusual unauthenticated HTTP GET requests.
  • Confirm remediation status against IBM’s advisory, not version assumptions alone.
Prepared
Confidence
medium
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-2021-20539 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.3 (3.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.0 score

5.3Medium
CVSS 3.0 vector shape for CVE-2021-20539Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AC:L/AV:N/A:N/S:U/UI:N/C:L/I:N/PR:N/RL:O/RC:C/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 Pak for Security1.6.0.0, 1.5.0.1, 1.5.0.0, 1.6.0.1, 1.7.0.0, 1.7.1.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.