Filtered by vendor Ibm Subscriptions
Filtered by product Concert Subscriptions
Total 8 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2024-37070 1 Ibm 1 Concert 2024-11-20 4.3 Medium
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could allow an authenticated user to obtain sensitive information that could aid in further attacks against the system.
CVE-2024-52359 1 Ibm 1 Concert 2024-11-20 4.3 Medium
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could allow an authenticated user to perform unauthorized actions that should be reserved to administrator used due to improper access controls.
CVE-2024-52360 1 Ibm 1 Concert 2024-11-20 7.6 High
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
CVE-2024-43189 1 Ibm 1 Concert 2024-11-18 5.9 Medium
IBM Concert Software 1.0.0 through 1.0.1 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 the middle techniques.
CVE-2024-41785 1 Ibm 1 Concert 2024-11-18 6.1 Medium
IBM Concert Software 1.0.0 through 1.0.1 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
CVE-2024-43177 1 Ibm 1 Concert 2024-10-25 5.9 Medium
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute.
CVE-2024-43173 1 Ibm 1 Concert 2024-10-25 3.7 Low
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute.
CVE-2024-43180 1 Ibm 1 Concert 2024-09-20 4.3 Medium
IBM Concert 1.0 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.