dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2021-39013

MEDIUM · 6.5 CVSS v3.1 Published 2021-12-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Cloud Pak for Security (CP4S) 1.7.2.0, 1.7.1.0, and 1.7.0.0 could allow an authenticated user to obtain sensitive information in HTTP responses that could be used in further attacks against the system. IBM X-Force ID: 213651.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Cloud Pak for Security versions 1.7.0.0 through 1.7.2.0 contains an information disclosure vulnerability where authenticated users can obtain sensitive information from HTTP responses. This exposed data could be used to plan further attacks against the system.

MitigationApply IBM security patches for CVE-2021-39013 or upgrade to a patched version of CP4S. If no patch available, conduct code review to identify and remediate endpoints returning sensitive data in HTTP responses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud Pak For SecurityApplication
Affected:= 1.7.0.0= 1.7.1.0= 1.7.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IBM Cloud Pak for Security is installed
    Check for CP4S deployment in your Kubernetes or OpenShift cluster using 'kubectl get pods | grep -i ibm' or by reviewing your installed operators
    Affected if CP4S is not present in the environment
  2. Identify the installed CP4S version
    Run 'kubectl get cp4s <cp4s-instance-name> -o jsonpath='{.spec.version}' or check the IBM Cloud Pak for Security operator version in your cluster's installed operators
    Affected if The installed version is 1.7.0.0, 1.7.1.0, or 1.7.2.0
  3. Verify authentication is enabled for CP4S
    Review CP4S authentication configuration by checking the platform authentication settings or reviewing user access controls via 'kubectl get platformauthentications'
    Affected if User authentication is configured and active
  4. Inspect HTTP response traffic for sensitive data exposure
    Capture and review HTTP responses from CP4S API endpoints using network logging, API gateway logs, or a web application firewall to identify if sensitive information such as internal paths, credentials, or system details are being returned in responses
    Affected if HTTP responses contain sensitive data not intended for the user
  5. Review audit logs for unauthorized information access
    Examine CP4S audit logs for patterns of users accessing data outside their normal scope, looking for repeated requests that retrieve verbose responses
    Affected if Audit logs show users accessing unexpected sensitive information in responses

You are affected if IBM Cloud Pak for Security versions 1.7.0.0, 1.7.1.0, or 1.7.2.0 are running and authenticated users can access HTTP responses containing sensitive information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM security patches for CVE-2021-39013 or upgrade to a patched version of CP4S. If no patch available, conduct code review to identify and remediate endpoints returning sensitive data in HTTP responses.

Recommended fix Moderate confidence

IBM Cloud Pak for Security 1.7.3.0 or later (or 1.8.0.0 if 1.7.3.x is not available)

  1. Check the current Cloud Pak for Security version by running: oc get cm -n ibm-cloudpak-security ibm-cp4s-deployment -o yaml | grep -i version
  2. If running 1.7.0.0, 1.7.1.0, or 1.7.2.0, plan for an upgrade to a fixed version
  3. Obtain the fixed version of IBM Cloud Pak for Security (1.7.3.0 or later) from IBM Fix Central or your IBM representative
  4. Back up all critical data and configurations before upgrading
  5. Follow the standard CP4S upgrade procedure: oc patch -n ibm-cloudpak-security ibm-cp4s-deployment --type merge -p '{"spec":{"version":"<fixed-version>"}}'
  6. Verify the upgrade completed successfully and the vulnerability is resolved
  7. Confirm the new version is running: oc get cm -n ibm-cloudpak-security ibm-cp4s-deployment -o yaml | grep -i version
Caveat Review IBM Cloud Pak for Security release notes for any configuration or data migration requirements between 1.7.x versions; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Pak For Security Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-39013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-39013 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data