{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-3025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-3025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-3025 is a high-severity vulnerability in n/a, published on 25 Nov 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-3025 and fix it if it is affected.\n\nWhat it is: CVE-2016-3025 is a high-severity vulnerability in n/a, published on 25 Nov 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-3025 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2016-3025/ (Markdown: https://insights.sbomify.com/CVE-2016-3025/index.md)","id":"CVE-2016-3025","markdown":"https://insights.sbomify.com/CVE-2016-3025/index.md","name":"CVE-2016-3025","record":{"aliases":["GHSA-hg84-67gc-4chq"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Access Manager","requires_auth":"none","summary":"Remote attackers can bypass failed login restrictions to perform brute-force attacks and gain unauthorized access to IBM Security Access Manager accounts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_access_manager","vendor":"ibm"},{"product":"security_access_manager_for_mobile","vendor":"ibm"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-254","name":null}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2016-3025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":4,"next":{"headline":"XML external entity in Access Manager","id":"CVE-2016-3027"},"packages":[],"prev":{"headline":"Information disclosure in Access Manager","id":"CVE-2016-3024"},"products":["n/a"],"published":"2016-11-25","related":[{"cvss_score":10,"headline":"Code injection in Security Access Manager Appliance","id":"CVE-2018-1722","kev_date_added":null,"published":"2018-08-24"},{"cvss_score":9.1,"headline":"Command injection in n/a","id":"CVE-2016-3028","kev_date_added":null,"published":"2016-11-25"},{"cvss_score":8.8,"headline":"Missing authorization in Security Access Manager Appliance","id":"CVE-2018-1850","kev_date_added":null,"published":"2018-10-22"},{"cvss_score":7.8,"headline":"IBM Security Access Manager Docker privilege escalation","id":"CVE-2023-30997","kev_date_added":null,"published":"2024-06-27"},{"cvss_score":7.8,"headline":"IBM Security Access Manager Docker privilege escalation","id":"CVE-2023-30998","kev_date_added":null,"published":"2024-06-27"},{"cvss_score":7.7,"headline":"Information disclosure in Security Access Manager","id":"CVE-2019-4145","kev_date_added":null,"published":"2019-06-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can bypass failed login restrictions to perform brute-force attacks and gain unauthorized access to IBM Security Access Manager accounts.","url":"https://insights.sbomify.com/CVE-2016-3025/"}