CVE-2016-3025

CVE-2016-3025 is a high-severity vulnerability in Ibm Security Access Manager with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-254.

Key facts

Description

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.

Frequently asked questions

What is CVE-2016-3025?
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.
How severe is CVE-2016-3025?
CVE-2016-3025 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2016-3025 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-3025?
CVE-2016-3025 primarily affects Ibm Security Access Manager. In total, 13 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-3025?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-3025 published?
CVE-2016-3025 was published on 2016-11-25 and last updated on 2026-06-17.

References

Affected products (13)

More vulnerabilities in Ibm Security Access Manager

All CVEs affecting Ibm Security Access Manager →

Other CWE-254 vulnerabilities

Browse all CWE-254 vulnerabilities →