What is the severity of CVE-2020-4820?

CVE-2020-4820 is classified as a high severity vulnerability due to its potential for allowing credential disclosure.

How do I fix CVE-2020-4820?

To fix CVE-2020-4820, upgrade IBM Cloud Pak for Security to a version beyond 1.4.0.0 that includes the security patch.

What types of attacks can CVE-2020-4820 facilitate?

CVE-2020-4820 can facilitate cross-site scripting attacks, allowing attackers to execute arbitrary JavaScript in the context of a user's session.

Who is affected by CVE-2020-4820?

Those using IBM Cloud Pak for Security version 1.4.0.0 are affected by CVE-2020-4820.

Is CVE-2020-4820 a potential risk for data security?

Yes, CVE-2020-4820 poses a risk to data security as it can lead to credentials exposure within a trusted session.

Vulnerability/
CVE-2020-4820

medium

6.1

CWE

11/12/2020

26/1/2021

4/8/2024

CVE-2020-4820: XSS

First published: Fri Dec 11 2020(Updated: )

IBM Cloud Pak for Security (CP4S) 1.4.0.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

Credit: psirt@us.ibm.com

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

Remedy

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

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

IBM-6408664

Frequently Asked Questions

What is the severity of CVE-2020-4820?
CVE-2020-4820 is classified as a high severity vulnerability due to its potential for allowing credential disclosure.
How do I fix CVE-2020-4820?
To fix CVE-2020-4820, upgrade IBM Cloud Pak for Security to a version beyond 1.4.0.0 that includes the security patch.
What types of attacks can CVE-2020-4820 facilitate?
CVE-2020-4820 can facilitate cross-site scripting attacks, allowing attackers to execute arbitrary JavaScript in the context of a user's session.
Who is affected by CVE-2020-4820?
Those using IBM Cloud Pak for Security version 1.4.0.0 are affected by CVE-2020-4820.
Is CVE-2020-4820 a potential risk for data security?
Yes, CVE-2020-4820 poses a risk to data security as it can lead to credentials exposure within a trusted session.

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

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-4820?
CVE-2020-4820 is classified as a high severity vulnerability due to its potential for allowing credential disclosure.
How do I fix CVE-2020-4820?
To fix CVE-2020-4820, upgrade IBM Cloud Pak for Security to a version beyond 1.4.0.0 that includes the security patch.
What types of attacks can CVE-2020-4820 facilitate?
CVE-2020-4820 can facilitate cross-site scripting attacks, allowing attackers to execute arbitrary JavaScript in the context of a user's session.
Who is affected by CVE-2020-4820?
Those using IBM Cloud Pak for Security version 1.4.0.0 are affected by CVE-2020-4820.
Is CVE-2020-4820 a potential risk for data security?
Yes, CVE-2020-4820 poses a risk to data security as it can lead to credentials exposure within a trusted session.