← Back

Security Verify Access

security_verify_access

Vendor: Ibm • 102 CVEs

CVEs (102)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Ibm
2Security Verify Access
Security Verify Access Docker
Jun 17, 2026
Aug 29, 2024
N/A· v4
8.2 HIGH· v3
N/A· v2
IBM Security Verify Access 10.0.0 through 10.0.8 OIDC Provider could allow a remote authenticated attacker to conduct phishing attacks, using an open redirect attack. By persuading a victim to visit a specially crafted W...Show more
IBM Security Verify Access 10.0.0 through 10.0.8 OIDC Provider could allow a remote authenticated attacker to conduct phishing attacks, using an open redirect attack. By persuading a victim to visit a specially crafted Web site, a remote attacker could exploit this vulnerability to spoof the URL displayed to redirect a user to a malicious Web site that would appear to be trusted. This could allow the attacker to obtain highly sensitive information or conduct further attacks against the victim.Show less
1Ibm
3Security Directory Integrator
Security Directory ServerSecurity Verify Access
Jun 17, 2026
Jul 25, 2024
N/A· v4
5.4 MEDIUM· v3
N/A· v2
IBM Security Directory Integrator 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 is vulnerable to stored cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI t...Show more
IBM Security Directory Integrator 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 is vulnerable to stored cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 285645.Show less
1Ibm
3Security Directory Integrator
Security Directory ServerSecurity Verify Access
Jun 17, 2026
Jul 25, 2024
N/A· v4
7.5 HIGH· v3
N/A· v2
IBM Security Directory Integrator 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 uses insufficient session expiration which could allow an unauthorized user to obtain sensitive information. IBM X-Force ID: 2...Show more
IBM Security Directory Integrator 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 uses insufficient session expiration which could allow an unauthorized user to obtain sensitive information. IBM X-Force ID: 228565.Show less
1Ibm
1Security Verify Access
Jun 17, 2026
Jun 27, 2024
N/A· v4
5.9 MEDIUM· v3
N/A· v2
IBM Security Verify Access 10.0.0.0 through 10.0.7.1, under certain configurations, could allow an unauthenticated attacker to cause a denial of service due to asymmetric resource consumption. IBM X-Force ID: 287615.
1Ibm
1Security Verify Access
Jun 17, 2026
Jun 27, 2024
N/A· v4
5.5 MEDIUM· v3
N/A· v2
IBM Security Verify Access 10.0.0 through 10.0.7.1 could allow a local user to obtain sensitive information from trace logs. IBM X-Force ID: 252183.
1Ibm
1Security Verify Access
Jun 17, 2026
Apr 10, 2024
N/A· v4
5.5 MEDIUM· v3
N/A· v2
IBM Security Verify Access Appliance 10.0.0 through 10.0.7 uses uninitialized variables when deploying that could allow a local user to cause a denial of service. IBM X-Force ID: 287318.
1Ibm
1Security Verify Access
Jun 17, 2026
Apr 10, 2024
N/A· v4
7.5 HIGH· v3
N/A· v2
IBM Security Verify Access Appliance 10.0.0 through 10.0.7 contains hard-coded credentials which it uses for its own inbound authentication that could be obtained by a malicious actor. IBM X-Force ID: 287317.
1Ibm
1Security Verify Access
Jun 17, 2026
Apr 10, 2024
N/A· v4
8.1 HIGH· v3
N/A· v2
IBM Security Verify Access Appliance 10.0.0 through 10.0.7 could allow a malicious actor to conduct a man in the middle attack when deploying Open Source scripts due to missing certificate validation. IBM X-Force ID: 2...Show more
IBM Security Verify Access Appliance 10.0.0 through 10.0.7 could allow a malicious actor to conduct a man in the middle attack when deploying Open Source scripts due to missing certificate validation. IBM X-Force ID: 287316.Show less
1Ibm
1Security Verify Access
Jun 17, 2026
Apr 10, 2024
N/A· v4
8.1 HIGH· v3
N/A· v2
IBM Security Verify Access Appliance 10.0.0 through 10.0.7 could allow a malicious actor to conduct a man in the middle attack when deploying Python scripts due to improper certificate validation. IBM X-Force ID: 28730...Show more
IBM Security Verify Access Appliance 10.0.0 through 10.0.7 could allow a malicious actor to conduct a man in the middle attack when deploying Python scripts due to improper certificate validation. IBM X-Force ID: 287306.Show less
1Ibm
2Application Gateway
Security Verify Access
Jun 17, 2026
Apr 4, 2024
N/A· v4
10.0 CRITICAL· v3
N/A· v2
IBM Security Verify Access 10.0.0 through 10.0.7 and IBM Application Gateway 20.01 through 24.03 could allow a remote attacker to obtain highly sensitive private information or cause a denial of service using a specially...Show more
IBM Security Verify Access 10.0.0 through 10.0.7 and IBM Application Gateway 20.01 through 24.03 could allow a remote attacker to obtain highly sensitive private information or cause a denial of service using a specially crafted HTTP request. IBM X-Force ID: 286584.Show less
1Ibm
1Security Verify Access
Jun 17, 2026
Mar 31, 2024
N/A· v4
5.5 MEDIUM· v3
N/A· v2
IBM Security Verify Access 10.0.6 could disclose sensitive snapshot information due to missing encryption. IBM X-Force ID: 281607.
1Ibm
1Security Verify Access
Jun 17, 2026
Feb 7, 2024
N/A· v4
7.2 HIGH· v3
N/A· v2
IBM Security Verify Access 10.0.0.0 through 10.0.6.1 could allow a privileged user to install a configuration file that could allow remote access. IBM X-Force ID: 266155.
1Ibm
1Security Verify Access
Jun 17, 2026
Feb 7, 2024
N/A· v4
9.8 CRITICAL· v3
N/A· v2
IBM Security Verify Access 10.0.0.0 through 10.0.6.1 uses insecure calls that could allow an attacker on the network to take control of the server. IBM X-Force ID: 254977.
1Ibm
1Security Verify Access
Jun 17, 2026
Feb 7, 2024
N/A· v4
9.8 CRITICAL· v3
N/A· v2
IBM Security Verify Access 10.0.0.0 through 10.0.6.1 uses insecure protocols in some instances that could allow an attacker on the network to take control of the server. IBM X-Force Id: 254957.
1Ibm
2Security Verify Access
Security Verify Access Docker
Jun 17, 2026
Feb 3, 2024
N/A· v4
7.3 HIGH· v3
N/A· v2
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a remote user to log into the server due...Show more
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a remote user to log into the server due to a user account with an empty password. IBM X-Force ID: 266154.Show less
1Ibm
2Security Verify Access
Security Verify Access Docker
Jun 17, 2026
Feb 3, 2024
N/A· v4
5.5 MEDIUM· v3
N/A· v2
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a user to download files from an incorrec...Show more
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a user to download files from an incorrect repository due to improper file validation. IBM X-Force ID: 254972.Show less
1Ibm
2Security Verify Access
Security Verify Access Docker
Jun 17, 2026
Feb 3, 2024
N/A· v4
7.1 HIGH· v3
N/A· v2
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) is vulnerable to an XML External Entity Injection (XX...Show more
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 254783.Show less
1Ibm
2Security Verify Access
Security Verify Access Docker
Jun 17, 2026
Feb 3, 2024
N/A· v4
7.5 HIGH· v3
N/A· v2
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) is vulnerable to a denial of service attacks on the D...Show more
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) is vulnerable to a denial of service attacks on the DSC server. IBM X-Force ID: 254776.Show less
1Ibm
2Security Verify Access
Security Verify Access Docker
Jun 17, 2026
Feb 3, 2024
N/A· v4
7.8 HIGH· v3
N/A· v2
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a local user to escalate their privileges...Show more
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a local user to escalate their privileges due to an improper security configuration. IBM X-Force ID: 254767.Show less
1Ibm
2Security Verify Access
Security Verify Access Docker
Jun 17, 2026
Feb 3, 2024
N/A· v4
9.0 CRITICAL· v3
N/A· v2
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a remote attacker to gain access to the u...Show more
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a remote attacker to gain access to the underlying system using man in the middle techniques. IBM X-Force ID: 254765.Show less