CVE-2014-0869: Medium severity ibm algo credit limits vulnerability

Published Jul 7, 2014
·
Updated

The decrypt function in RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics does not require a key, which makes it easier for remote attackers to obtain cleartext passwords by sniffing the network and then providing a string argument to this function.

Affected Software

3 affected components
IBM Algo Credit Limits=4.5.0
IBM Algo Credit Limits=4.7.0
IBM Algorithmics

Event History

Jul 7, 2014
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2014-0869?

CVE-2014-0869 is considered a high severity vulnerability due to its potential to expose cleartext passwords.

2

How do I fix CVE-2014-0869?

To fix CVE-2014-0869, upgrade to IBM Algo Credit Limits version 4.7.0.03 FP5 or later.

3

What are the affected versions related to CVE-2014-0869?

CVE-2014-0869 affects IBM Algo Credit Limits versions 4.5.0 through 4.7.0 before 4.7.0.03 FP5.

4

What types of attacks can exploit CVE-2014-0869?

CVE-2014-0869 can be exploited by remote attackers sniffing the network to obtain cleartext passwords.

5

Is there a workaround for CVE-2014-0869?

There are no documented workarounds for CVE-2014-0869; the recommended action is to upgrade the software.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203