VYPR

Security Verify Information Queue

by IBM

CVEs (36)

  • CVE-2022-35286HigJul 26, 2022
    risk 0.57cvss 8.8epss 0.00

    IBM Security Verify Information Queue 10.0.2 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 230814.

  • CVE-2022-35285HigJul 25, 2022
    risk 0.57cvss 8.8epss 0.00

    IBM Security Verify Information Queue 10.0.2 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 230812.

  • CVE-2021-20403HigFeb 11, 2021
    risk 0.57cvss 8.8epss 0.00

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.

  • CVE-2020-4283HigMar 2, 2020
    risk 0.56cvss 8.6epss 0.01

    IBM Security Information Queue (ISIQ) 1.0.0, 1.0.1, 1.0.2, 1.0.3, and 1.0.4 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.…

  • CVE-2021-20411HigFeb 12, 2021
    risk 0.53cvss 8.1epss 0.00

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 could allow a user to impersonate another user on the system due to incorrectly updating the session identifier. IBM X-Force ID: 198191.

  • CVE-2022-35287HigJul 25, 2022
    risk 0.49cvss 7.5epss 0.01

    IBM Security Verify Information Queue 10.0.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 230817.

  • CVE-2022-35284HigJul 25, 2022
    risk 0.49cvss 7.5epss 0.01

    IBM Security Verify Information Queue 10.0.2 could disclose sensitive information due to a missing or insecure SameSite attribute for a sensitive cookie. IBM X-Force ID: 230811.

  • CVE-2021-20412HigFeb 12, 2021
    risk 0.49cvss 7.5epss 0.01

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 198192.

  • CVE-2021-20405HigFeb 11, 2021
    risk 0.49cvss 7.5epss 0.01

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 could allow a user to perform unauthorized activities due to improper encoding of output. IBM X-Force ID: 196183.

  • CVE-2019-4162HigJun 6, 2019
    risk 0.49cvss 7.5epss 0.01

    IBM Security Information Queue (ISIQ) 1.0.0, 1.0.1, and 1.0.2 is missing the HTTP Strict Transport Security header. Users can navigate by mistake to the unencrypted version of the web application or accept invalid certificates. This leads to sensitive data being sent unencrypted…

  • CVE-2022-35288MedJul 25, 2022
    risk 0.42cvss 6.5epss 0.01

    IBM Security Verify Information Queue 10.0.2 could allow a user to obtain sensitive information that could be used in further attacks against the system. IBM X-Force ID: 230818.

  • CVE-2022-35283MedJul 14, 2022
    risk 0.42cvss 6.5epss 0.01

    IBM Security Verify Information Queue 10.0.2 could allow an authenticated user to cause a denial of service with a specially crafted HTTP request.

  • CVE-2019-4217MedJun 6, 2019
    risk 0.40cvss 6.1epss 0.01

    IBM Security Information Queue (ISIQ) 1.0.0, 1.0.1, and 1.0.2 could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions…

  • CVE-2021-20409MedFeb 12, 2021
    risk 0.38cvss 5.9epss 0.01

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in…

  • CVE-2021-20408MedFeb 12, 2021
    risk 0.36cvss 5.5epss 0.00

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 could disclose highly sensitive information to a local user due to inproper storage of a plaintext cryptographic key. IBM X-Force ID: 198187.

  • CVE-2021-20410MedFeb 12, 2021
    risk 0.35cvss 5.3epss 0.01

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 sends user credentials in plain clear text which can be read by an authenticated user using man in the middle techniques. IBM X-Force ID: 198190.

  • CVE-2021-20407MedFeb 12, 2021
    risk 0.35cvss 5.3epss 0.01

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 discloses sensitive information in source code that could be used in further attacks against the system. IBM X-Force ID: 196185.

  • CVE-2021-20404MedFeb 11, 2021
    risk 0.35cvss 5.3epss 0.01

    IBM Security Verify Information Queue 1.0.6 and 1.0.7 could allow a user on the network to cause a denial of service due to an invalid cookie value that could prevent future logins. IBM X-Force ID: 196078.

  • CVE-2020-4290MedApr 8, 2020
    risk 0.35cvss 5.4epss 0.01

    IBM Security Information Queue (ISIQ) 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, and 1.0.5 could allow any authenticated user to spoof the configuration owner of any other user which disclose sensitive information or allow for unauthorized access. IBM X-Force ID: 176333.

  • CVE-2020-4289MedApr 8, 2020
    risk 0.35cvss 5.3epss 0.02

    IBM Security Information Queue (ISIQ) 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, and 1.0.5 could allow a remote attacker to obtain sensitive information, caused by the failure to set the HTTPOnly flag. A remote attacker could exploit this vulnerability to obtain sensitive information…

Page 1 of 2