What is the severity of CVE-2017-1231?

CVE-2017-1231 is considered to have a medium severity due to the exposure of user credentials.

How do I fix CVE-2017-1231?

To fix CVE-2017-1231, update the IBM BigFix Platform to a version higher than 9.5.9 that addresses the credential storage issue.

What versions of IBM BigFix Platform are affected by CVE-2017-1231?

IBM BigFix Platform versions from 9.5 to 9.5.9 are affected by CVE-2017-1231.

What are the potential impacts of CVE-2017-1231?

The impact of CVE-2017-1231 includes unauthorized access to user credentials, compromising the security of the affected system.

Is there a workaround for CVE-2017-1231?

While the recommended solution is to upgrade the software, limiting user access to the system can act as a temporary workaround for CVE-2017-1231.

Vulnerability/
CVE-2017-1231

high

7.8

CWE

522

12/10/2018

17/9/2024

CVE-2017-1231

First published: Fri Oct 12 2018(Updated: )

IBM BigFix Platform 9.5 - 9.5.9 stores user credentials in plain in clear text which can be read by a local user. IBM X-Force ID: 123910.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM BigFix Platform	>=9.5<=9.5.9

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-1231?
CVE-2017-1231 is considered to have a medium severity due to the exposure of user credentials.
How do I fix CVE-2017-1231?
To fix CVE-2017-1231, update the IBM BigFix Platform to a version higher than 9.5.9 that addresses the credential storage issue.
What versions of IBM BigFix Platform are affected by CVE-2017-1231?
IBM BigFix Platform versions from 9.5 to 9.5.9 are affected by CVE-2017-1231.
What are the potential impacts of CVE-2017-1231?
The impact of CVE-2017-1231 includes unauthorized access to user credentials, compromising the security of the affected system.
Is there a workaround for CVE-2017-1231?
While the recommended solution is to upgrade the software, limiting user access to the system can act as a temporary workaround for CVE-2017-1231.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/author
agent/weakness
agent/severity
agent/description
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
vendor/ibm
canonical/ibm bigfix platform
version/ibm bigfix platform/9.5
version/ibm bigfix platform/9.5.9

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-1231?
CVE-2017-1231 is considered to have a medium severity due to the exposure of user credentials.
How do I fix CVE-2017-1231?
To fix CVE-2017-1231, update the IBM BigFix Platform to a version higher than 9.5.9 that addresses the credential storage issue.
What versions of IBM BigFix Platform are affected by CVE-2017-1231?
IBM BigFix Platform versions from 9.5 to 9.5.9 are affected by CVE-2017-1231.
What are the potential impacts of CVE-2017-1231?
The impact of CVE-2017-1231 includes unauthorized access to user credentials, compromising the security of the affected system.
Is there a workaround for CVE-2017-1231?
While the recommended solution is to upgrade the software, limiting user access to the system can act as a temporary workaround for CVE-2017-1231.