First published: Fri 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.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle Access Manager | =9.0.0 | |
Oracle Access Manager | =9.0.0.1 | |
Oracle 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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-3025 is classified as a medium severity vulnerability due to its potential for exploitation through brute-force attacks.
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.
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.
CVE-2016-3025 allows remote attackers to perform brute-force attacks due to insufficient restrictions on failed login attempts.
There are no specific workarounds for CVE-2016-3025, and upgrading to the patched versions is the recommended mitigation.