What is the severity of CVE-2020-4967?

CVE-2020-4967 has a medium severity rating due to its potential to disclose sensitive information.

How do I fix CVE-2020-4967?

To fix CVE-2020-4967, you should update IBM Cloud Pak for Security to the latest version that addresses this vulnerability.

What systems are affected by CVE-2020-4967?

CVE-2020-4967 affects IBM Cloud Pak for Security version 1.3.0.1 and potentially earlier versions.

What information is disclosed in CVE-2020-4967?

CVE-2020-4967 can disclose sensitive information through HTTP headers, which can be leveraged for further attacks.

Is there a workaround for CVE-2020-4967?

Currently, no specific workarounds have been publicly recommended for CVE-2020-4967, so updating the software is advised.

Vulnerability/
CVE-2020-4967

medium

4.3

CWE

200

11/12/2020

26/1/2021

4/8/2024

CVE-2020-4967: Infoleak

First published: Fri Dec 11 2020(Updated: )

IBM Cloud Pak for Security (CP4S) 1.3.0.1 could disclose sensitive information through HTTP headers which could be used in further attacks against the system. IBM X-Force ID: 192425.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
	=1.3.0.1
	<=1.3.0.1

Remedy

https://www.ibm.com/support/pages/node/6408662

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

IBM-6408662

Frequently Asked Questions

What is the severity of CVE-2020-4967?
CVE-2020-4967 has a medium severity rating due to its potential to disclose sensitive information.
How do I fix CVE-2020-4967?
To fix CVE-2020-4967, you should update IBM Cloud Pak for Security to the latest version that addresses this vulnerability.
What systems are affected by CVE-2020-4967?
CVE-2020-4967 affects IBM Cloud Pak for Security version 1.3.0.1 and potentially earlier versions.
What information is disclosed in CVE-2020-4967?
CVE-2020-4967 can disclose sensitive information through HTTP headers, which can be leveraged for further attacks.
Is there a workaround for CVE-2020-4967?
Currently, no specific workarounds have been publicly recommended for CVE-2020-4967, so updating the software is advised.

collector/nvd-index
agent/type
agent/references
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/remedy
agent/last-modified-date
agent/author
agent/description
agent/softwarecombine
agent/event
collector/ibm-support
source/IBM
agent/software-canonical-lookup
agent/trending
agent/tags
agent/source
vendor/ibm
canonical/ibm cloud pak for security (cp4s)
version/ibm cloud pak for security (cp4s)/1.3.0.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-4967?
CVE-2020-4967 has a medium severity rating due to its potential to disclose sensitive information.
How do I fix CVE-2020-4967?
To fix CVE-2020-4967, you should update IBM Cloud Pak for Security to the latest version that addresses this vulnerability.
What systems are affected by CVE-2020-4967?
CVE-2020-4967 affects IBM Cloud Pak for Security version 1.3.0.1 and potentially earlier versions.
What information is disclosed in CVE-2020-4967?
CVE-2020-4967 can disclose sensitive information through HTTP headers, which can be leveraged for further attacks.
Is there a workaround for CVE-2020-4967?
Currently, no specific workarounds have been publicly recommended for CVE-2020-4967, so updating the software is advised.