What is the severity of CVE-2017-1196?

The severity of CVE-2017-1196 is considered moderate due to weak password requirements that can lead to account compromise.

How do I fix CVE-2017-1196?

To fix CVE-2017-1196, implement a policy that enforces strong password requirements for users.

What version of IBM BigFix Compliance is affected by CVE-2017-1196?

IBM BigFix Compliance version 1.9.70 is affected by CVE-2017-1196.

What is the impact of CVE-2017-1196 on user accounts?

CVE-2017-1196 allows attackers to more easily compromise user accounts due to the absence of strong password enforcement.

Is there a workaround for CVE-2017-1196?

A workaround for CVE-2017-1196 is to manually enforce strong password policies until an official patch is available.

Vulnerability/
CVE-2017-1196

critical

9.8

CWE

521

7/6/2017

5/8/2024

CVE-2017-1196

First published: Wed Jun 07 2017(Updated: )

IBM BigFix Compliance (TEMA SUAv1 SCA SCM) 1.9.70 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 123671.

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-1196?
The severity of CVE-2017-1196 is considered moderate due to weak password requirements that can lead to account compromise.
How do I fix CVE-2017-1196?
To fix CVE-2017-1196, implement a policy that enforces strong password requirements for users.
What version of IBM BigFix Compliance is affected by CVE-2017-1196?
IBM BigFix Compliance version 1.9.70 is affected by CVE-2017-1196.
What is the impact of CVE-2017-1196 on user accounts?
CVE-2017-1196 allows attackers to more easily compromise user accounts due to the absence of strong password enforcement.
Is there a workaround for CVE-2017-1196?
A workaround for CVE-2017-1196 is to manually enforce strong password policies until an official patch is available.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/references
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-1196?
The severity of CVE-2017-1196 is considered moderate due to weak password requirements that can lead to account compromise.
How do I fix CVE-2017-1196?
To fix CVE-2017-1196, implement a policy that enforces strong password requirements for users.
What version of IBM BigFix Compliance is affected by CVE-2017-1196?
IBM BigFix Compliance version 1.9.70 is affected by CVE-2017-1196.
What is the impact of CVE-2017-1196 on user accounts?
CVE-2017-1196 allows attackers to more easily compromise user accounts due to the absence of strong password enforcement.
Is there a workaround for CVE-2017-1196?
A workaround for CVE-2017-1196 is to manually enforce strong password policies until an official patch is available.