What is the severity of CVE-2017-1224?

CVE-2017-1224 is considered a moderate severity vulnerability due to its potential impact on sensitive information.

How do I fix CVE-2017-1224?

To fix CVE-2017-1224, upgrade to the latest version of IBM Tivoli Endpoint Manager that addresses the weak cryptographic algorithms.

What systems are affected by CVE-2017-1224?

CVE-2017-1224 affects specific versions of IBM BigFix Platform including 9.2.6, 9.2.7, and 9.5.x versions.

What type of attack does CVE-2017-1224 expose systems to?

CVE-2017-1224 may allow attackers to decrypt highly sensitive information due to weaker than expected cryptographic algorithms.

Is there a workaround for CVE-2017-1224?

There is no specific workaround mentioned for CVE-2017-1224; upgrading is the recommended approach to mitigate this vulnerability.

Vulnerability/
CVE-2017-1224

high

7.5

CWE

326

19/7/2017

17/9/2024

CVE-2017-1224: Weak Encryption

First published: Wed Jul 19 2017(Updated: )

IBM Tivoli Endpoint Manager uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 123903.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM BigFix Platform	=9.2.6
IBM BigFix Platform	=9.2.7
IBM BigFix Platform	=9.5
IBM BigFix Platform	=9.5.5
IBM BigFix Platform	=9.5.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-1224?
CVE-2017-1224 is considered a moderate severity vulnerability due to its potential impact on sensitive information.
How do I fix CVE-2017-1224?
To fix CVE-2017-1224, upgrade to the latest version of IBM Tivoli Endpoint Manager that addresses the weak cryptographic algorithms.
What systems are affected by CVE-2017-1224?
CVE-2017-1224 affects specific versions of IBM BigFix Platform including 9.2.6, 9.2.7, and 9.5.x versions.
What type of attack does CVE-2017-1224 expose systems to?
CVE-2017-1224 may allow attackers to decrypt highly sensitive information due to weaker than expected cryptographic algorithms.
Is there a workaround for CVE-2017-1224?
There is no specific workaround mentioned for CVE-2017-1224; upgrading is the recommended approach to mitigate this vulnerability.

collector/nvd-index
agent/type
agent/softwarecombine
agent/author
agent/weakness
agent/severity
agent/references
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.2.6
version/ibm bigfix platform/9.2.7
version/ibm bigfix platform/9.5
version/ibm bigfix platform/9.5.5
version/ibm bigfix platform/9.5.6

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-1224?
CVE-2017-1224 is considered a moderate severity vulnerability due to its potential impact on sensitive information.
How do I fix CVE-2017-1224?
To fix CVE-2017-1224, upgrade to the latest version of IBM Tivoli Endpoint Manager that addresses the weak cryptographic algorithms.
What systems are affected by CVE-2017-1224?
CVE-2017-1224 affects specific versions of IBM BigFix Platform including 9.2.6, 9.2.7, and 9.5.x versions.
What type of attack does CVE-2017-1224 expose systems to?
CVE-2017-1224 may allow attackers to decrypt highly sensitive information due to weaker than expected cryptographic algorithms.
Is there a workaround for CVE-2017-1224?
There is no specific workaround mentioned for CVE-2017-1224; upgrading is the recommended approach to mitigate this vulnerability.