What is the severity of CVE-2017-1256?

CVE-2017-1256 is considered a medium severity vulnerability due to its potential to allow cross-site scripting.

How do I fix CVE-2017-1256?

To fix CVE-2017-1256, you should upgrade IBM Security Guardium to the latest version that addresses this vulnerability.

Who is affected by CVE-2017-1256?

CVE-2017-1256 affects users of IBM Security Guardium versions 10.0 and 10.1.

What are the risks associated with CVE-2017-1256?

The risks of CVE-2017-1256 include the possibility of credential disclosure through the execution of arbitrary JavaScript within the web UI.

Is there a workaround for CVE-2017-1256?

Currently, the recommended approach is to upgrade the affected software versions, as no specific workarounds have been provided for CVE-2017-1256.

Vulnerability/
CVE-2017-1256

medium

6.1

CWE

5/7/2017

17/9/2024

CVE-2017-1256: XSS

First published: Wed Jul 05 2017(Updated: )

IBM Security Guardium 10.0, 10.1 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. IBM X-Force ID: 124678

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM InfoSphere Guardium z/OS	=10.0
IBM InfoSphere Guardium z/OS	=10.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-1256?
CVE-2017-1256 is considered a medium severity vulnerability due to its potential to allow cross-site scripting.
How do I fix CVE-2017-1256?
To fix CVE-2017-1256, you should upgrade IBM Security Guardium to the latest version that addresses this vulnerability.
Who is affected by CVE-2017-1256?
CVE-2017-1256 affects users of IBM Security Guardium versions 10.0 and 10.1.
What are the risks associated with CVE-2017-1256?
The risks of CVE-2017-1256 include the possibility of credential disclosure through the execution of arbitrary JavaScript within the web UI.
Is there a workaround for CVE-2017-1256?
Currently, the recommended approach is to upgrade the affected software versions, as no specific workarounds have been provided for CVE-2017-1256.

agent/type
agent/author
agent/weakness
agent/severity
agent/references
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/ibm
canonical/ibm infosphere guardium z/os
version/ibm infosphere guardium z/os/10.0
version/ibm infosphere guardium z/os/10.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-2017-1256?
CVE-2017-1256 is considered a medium severity vulnerability due to its potential to allow cross-site scripting.
How do I fix CVE-2017-1256?
To fix CVE-2017-1256, you should upgrade IBM Security Guardium to the latest version that addresses this vulnerability.
Who is affected by CVE-2017-1256?
CVE-2017-1256 affects users of IBM Security Guardium versions 10.0 and 10.1.
What are the risks associated with CVE-2017-1256?
The risks of CVE-2017-1256 include the possibility of credential disclosure through the execution of arbitrary JavaScript within the web UI.
Is there a workaround for CVE-2017-1256?
Currently, the recommended approach is to upgrade the affected software versions, as no specific workarounds have been provided for CVE-2017-1256.