CVE-2016-3025: High severity oracle access manager vulnerability

Published Nov 25, 2016
·
Updated

IBM Security Access Manager for Mobile 8.x before 8.0.1.4 IF3 and Security Access Manager 9.x before 9.0.1.0 IF5 do not properly restrict failed login attempts, which makes it easier for remote attackers to obtain access via a brute-force approach.

Affected Software

13 affected components
IBM Security Access Manager=9.0.0
IBM Security Access Manager=9.0.0.1
IBM Security Access Manager=9.0.1.0
IBM Security Access Manager for Mobile=8.0.0.0
IBM Security Access Manager for Mobile=8.0.0.1
IBM Security Access Manager for Mobile=8.0.0.2
IBM Security Access Manager for Mobile=8.0.0.3
IBM Security Access Manager for Mobile=8.0.0.4
IBM Security Access Manager for Mobile=8.0.0.5
IBM Security Access Manager for Mobile=8.0.1
IBM Security Access Manager for Mobile=8.0.1.2
IBM Security Access Manager for Mobile=8.0.1.3
IBM Security Access Manager for Mobile=8.0.1.4

Event History

Nov 25, 2016
CVE Published
via MITRE·03:38 AM
Data Sourced
via MITRE·03:38 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-2016-3025?

CVE-2016-3025 is classified as a medium severity vulnerability due to its potential for exploitation through brute-force attacks.

2

How do I fix CVE-2016-3025?

To fix CVE-2016-3025, update your IBM Security Access Manager for Mobile or Security Access Manager to versions 8.0.1.4 IF3 or 9.0.1.0 IF5 or later.

3

Which versions are affected by CVE-2016-3025?

Versions of IBM Security Access Manager for Mobile prior to 8.0.1.4 IF3 and Security Access Manager versions before 9.0.1.0 IF5 are affected by CVE-2016-3025.

4

What type of attack does CVE-2016-3025 enable?

CVE-2016-3025 allows remote attackers to perform brute-force attacks due to insufficient restrictions on failed login attempts.

5

Is there a workaround for CVE-2016-3025?

There are no specific workarounds for CVE-2016-3025, and upgrading to the patched versions is the recommended mitigation.

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