What is the severity of CVE-2017-1258?

CVE-2017-1258 is considered a critical vulnerability due to the lack of authentication checks allowing unauthorized access.

How do I fix CVE-2017-1258?

To fix CVE-2017-1258, upgrade to IBM Security Guardium version 10.1.2 or later.

What versions of IBM Security Guardium are affected by CVE-2017-1258?

CVE-2017-1258 affects IBM Security Guardium versions 10.0, 10.0.1, and 10.1.

Can CVE-2017-1258 lead to data breaches?

Yes, CVE-2017-1258 can potentially lead to data breaches by allowing anonymous users access to protected areas.

What types of access does CVE-2017-1258 compromise?

CVE-2017-1258 compromises access to critical resources or functionalities within IBM Security Guardium.

Vulnerability/
CVE-2017-1258

medium

6.5

CWE

287

5/7/2017

16/9/2024

CVE-2017-1258

First published: Wed Jul 05 2017(Updated: )

IBM Security Guardium 10.0 and 10.1 does not perform an authentication check for a critical resource or functionality allowing anonymous users access to protected areas. IBM X-Force ID: 124685

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.0.1
IBM InfoSphere Guardium z/OS	=10.1
IBM InfoSphere Guardium z/OS	=10.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-1258?
CVE-2017-1258 is considered a critical vulnerability due to the lack of authentication checks allowing unauthorized access.
How do I fix CVE-2017-1258?
To fix CVE-2017-1258, upgrade to IBM Security Guardium version 10.1.2 or later.
What versions of IBM Security Guardium are affected by CVE-2017-1258?
CVE-2017-1258 affects IBM Security Guardium versions 10.0, 10.0.1, and 10.1.
Can CVE-2017-1258 lead to data breaches?
Yes, CVE-2017-1258 can potentially lead to data breaches by allowing anonymous users access to protected areas.
What types of access does CVE-2017-1258 compromise?
CVE-2017-1258 compromises access to critical resources or functionalities within IBM Security Guardium.

agent/type
agent/softwarecombine
agent/author
agent/weakness
agent/severity
agent/references
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
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.0.1
version/ibm infosphere guardium z/os/10.1
version/ibm infosphere guardium z/os/10.1.2

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-1258?
CVE-2017-1258 is considered a critical vulnerability due to the lack of authentication checks allowing unauthorized access.
How do I fix CVE-2017-1258?
To fix CVE-2017-1258, upgrade to IBM Security Guardium version 10.1.2 or later.
What versions of IBM Security Guardium are affected by CVE-2017-1258?
CVE-2017-1258 affects IBM Security Guardium versions 10.0, 10.0.1, and 10.1.
Can CVE-2017-1258 lead to data breaches?
Yes, CVE-2017-1258 can potentially lead to data breaches by allowing anonymous users access to protected areas.
What types of access does CVE-2017-1258 compromise?
CVE-2017-1258 compromises access to critical resources or functionalities within IBM Security Guardium.