What is the severity of CVE-2018-1475?

CVE-2018-1475 has a medium severity rating due to its potential to allow remote attackers to brute force account credentials.

How do I fix CVE-2018-1475?

To fix CVE-2018-1475, you should update IBM BigFix Platform to a version beyond 9.2.13 or 9.5.8 that addresses the account lockout settings.

Which versions of IBM BigFix Platform are affected by CVE-2018-1475?

CVE-2018-1475 affects IBM BigFix Platform versions 9.2 and 9.5 up to 9.2.13 and 9.5.8.

What is the impact of CVE-2018-1475?

The impact of CVE-2018-1475 allows remote attackers to exploit inadequate lockout settings to gain unauthorized access.

Is there a workaround for CVE-2018-1475?

Implementing stronger account lockout policies can act as a temporary workaround for CVE-2018-1475 until a software update is applied.

Vulnerability/
CVE-2018-1475

critical

9.8

CWE

307

27/4/2018

3/10/2019

CVE-2018-1475

First published: Fri Apr 27 2018(Updated: )

IBM BigFix Platform 9.2 and 9.5 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials. IBM X-Force ID: 140756.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM BigFix Platform	>=9.2<=9.2.13
IBM BigFix Platform	>=9.5<=9.5.8

Remedy

http://www.ibm.com/support/docview.wss?uid=swg22015754

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-1475?
CVE-2018-1475 has a medium severity rating due to its potential to allow remote attackers to brute force account credentials.
How do I fix CVE-2018-1475?
To fix CVE-2018-1475, you should update IBM BigFix Platform to a version beyond 9.2.13 or 9.5.8 that addresses the account lockout settings.
Which versions of IBM BigFix Platform are affected by CVE-2018-1475?
CVE-2018-1475 affects IBM BigFix Platform versions 9.2 and 9.5 up to 9.2.13 and 9.5.8.
What is the impact of CVE-2018-1475?
The impact of CVE-2018-1475 allows remote attackers to exploit inadequate lockout settings to gain unauthorized access.
Is there a workaround for CVE-2018-1475?
Implementing stronger account lockout policies can act as a temporary workaround for CVE-2018-1475 until a software update is applied.

collector/nvd-index
agent/references
agent/weakness
agent/severity
agent/author
agent/tags
agent/type
agent/event
agent/last-modified-date
agent/remedy
agent/softwarecombine
agent/first-publish-date
vendor/ibm
canonical/ibm bigfix platform
version/ibm bigfix platform/9.2
version/ibm bigfix platform/9.2.13
version/ibm bigfix platform/9.5
version/ibm bigfix platform/9.5.8

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-2018-1475?
CVE-2018-1475 has a medium severity rating due to its potential to allow remote attackers to brute force account credentials.
How do I fix CVE-2018-1475?
To fix CVE-2018-1475, you should update IBM BigFix Platform to a version beyond 9.2.13 or 9.5.8 that addresses the account lockout settings.
Which versions of IBM BigFix Platform are affected by CVE-2018-1475?
CVE-2018-1475 affects IBM BigFix Platform versions 9.2 and 9.5 up to 9.2.13 and 9.5.8.
What is the impact of CVE-2018-1475?
The impact of CVE-2018-1475 allows remote attackers to exploit inadequate lockout settings to gain unauthorized access.
Is there a workaround for CVE-2018-1475?
Implementing stronger account lockout policies can act as a temporary workaround for CVE-2018-1475 until a software update is applied.