Vulnerabilities > IBM > Security Verify Governance
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2023-01-09 | CVE-2022-22470 | Cleartext Storage of Sensitive Information vulnerability in IBM Security Verify Governance 10.0 IBM Security Verify Governance 10.0 stores user credentials in plain clear text which can be read by a local user. | 5.5 |
| 2022-12-24 | CVE-2022-22449 | Information Exposure Through an Error Message vulnerability in IBM Security Verify Governance 10.0.1 IBM Security Verify Governance, Identity Manager 10.01 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. | 5.3 |
| 2022-12-22 | CVE-2022-22456 | Cross-site Scripting vulnerability in IBM Security Verify Governance 10.0.1 IBM Security Verify Governance, Identity Manager 10.0.1 is vulnerable to cross-site scripting. | 6.1 |
| 2022-12-22 | CVE-2022-22457 | Cleartext Storage of Sensitive Information vulnerability in IBM Security Verify Governance 10.0.1 IBM Security Verify Governance, Identity Manager 10.0.1 stores sensitive information including user credentials in plain clear text which can be read by a local privileged user. | 4.4 |
| 2022-12-22 | CVE-2022-22458 | Insufficiently Protected Credentials vulnerability in IBM Security Verify Governance 10.0.1 IBM Security Verify Governance, Identity Manager 10.0.1 stores user credentials in plain clear text which can be read by a remote authenticated user. | 6.5 |
| 2022-12-22 | CVE-2022-22461 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Security Verify Governance 10.0.1 IBM Security Verify Governance, Identity Manager 10.0.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2022-12-22 | CVE-2022-35646 | Improper Authentication vulnerability in IBM Security Verify Governance 10.0.1 IBM Security Verify Governance, Identity Manager 10.0.1 software component could allow an authenticated user to modify or cancel any other user's access request using man-in-the-middle techniques. | 5.3 |