CVE-2018-1638: High severity IBM API Connect vulnerability

Published Jul 31, 2018
·
Updated

IBM API Connect 5.0.0.0-5.0.8.3 Developer Portal does not enforce Two Factor Authentication (TFA) while resetting a user password but enforces it for all other login scenarios. IBM X-Force ID: 144483.

Affected Software

1 affected component
IBM API Connect>=5.0.0.0<=5.0.8.3

Event History

Jul 31, 2018
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2018-1638?

CVE-2018-1638 has a medium severity rating due to the lack of Two Factor Authentication during password resets.

2

How do I fix CVE-2018-1638?

To mitigate CVE-2018-1638, ensure that Regular Two Factor Authentication is enforced for password resets within IBM API Connect.

3

What systems are affected by CVE-2018-1638?

CVE-2018-1638 affects IBM API Connect versions 5.0.0.0 to 5.0.8.3.

4

What potential risks are associated with CVE-2018-1638?

The primary risk of CVE-2018-1638 is that unauthorized users could exploit the password reset functionality without proper authentication, leading to account takeover.

5

Is there a workaround for CVE-2018-1638?

Until a patch is applied for CVE-2018-1638, administrators should manually enforce enhanced password security measures and closely monitor account activity.

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