What is the severity of CVE-2017-1197?

CVE-2017-1197 is considered a medium severity vulnerability due to the potential for brute force attacks on account credentials.

How do I fix CVE-2017-1197?

To fix CVE-2017-1197, update to a version of IBM BigFix Compliance that has addressed the inadequate account lockout settings.

What systems are affected by CVE-2017-1197?

CVE-2017-1197 affects IBM BigFix Compliance version 1.9.70.

Can CVE-2017-1197 lead to unauthorized access?

Yes, CVE-2017-1197 can allow a remote attacker to gain unauthorized access through brute force credential attempts.

Is there a workaround for CVE-2017-1197?

A potential workaround for CVE-2017-1197 includes implementing stricter account lockout policies on your systems.

Vulnerability/
CVE-2017-1197

critical

9.8

CWE

307

15/6/2017

5/8/2024

CVE-2017-1197

First published: Thu Jun 15 2017(Updated: )

IBM BigFix Compliance (TEMA SUAv1 SCA SCM) uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials. IBM X-Force ID: 123672.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
Ibm Bigfix Security Compliance Analytics	=1.9.70

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-1197?
CVE-2017-1197 is considered a medium severity vulnerability due to the potential for brute force attacks on account credentials.
How do I fix CVE-2017-1197?
To fix CVE-2017-1197, update to a version of IBM BigFix Compliance that has addressed the inadequate account lockout settings.
What systems are affected by CVE-2017-1197?
CVE-2017-1197 affects IBM BigFix Compliance version 1.9.70.
Can CVE-2017-1197 lead to unauthorized access?
Yes, CVE-2017-1197 can allow a remote attacker to gain unauthorized access through brute force credential attempts.
Is there a workaround for CVE-2017-1197?
A potential workaround for CVE-2017-1197 includes implementing stricter account lockout policies on your systems.

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

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-1197?
CVE-2017-1197 is considered a medium severity vulnerability due to the potential for brute force attacks on account credentials.
How do I fix CVE-2017-1197?
To fix CVE-2017-1197, update to a version of IBM BigFix Compliance that has addressed the inadequate account lockout settings.
What systems are affected by CVE-2017-1197?
CVE-2017-1197 affects IBM BigFix Compliance version 1.9.70.
Can CVE-2017-1197 lead to unauthorized access?
Yes, CVE-2017-1197 can allow a remote attacker to gain unauthorized access through brute force credential attempts.
Is there a workaround for CVE-2017-1197?
A potential workaround for CVE-2017-1197 includes implementing stricter account lockout policies on your systems.