Ibm Concert vulnerabilities

CVE-2025-36438 [MEDIUM] CWE-923 CVE-2025-36438: IBM Concert 1.0.0 through 2.2.0 could allow a privileged user to perform unauthorized actions due to IBM Concert 1.0.0 through 2.2.0 could allow a privileged user to perform unauthorized actions due to improper restriction of channel communication to intended endpoints.

CVE-2024-52893 [MEDIUM] CWE-209 CVE-2024-52893: IBM Concert Software 1.0.0, 1.0.1, 1.0.2, 1.0.2.1, and 1.0.3 could allow a remote attacker to obta IBM Concert Software 1.0.0, 1.0.1, 1.0.2, 1.0.2.1, and 1.0.3 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.

CVE-2025-36083 [MEDIUM] CWE-244 CVE-2025-36083: IBM Concert Software 1.0.0 through 2.0.0 could allow a local user to obtain sensitive information IBM Concert Software 1.0.0 through 2.0.0 could allow a local user to obtain sensitive information from buffers due to improper clearing of heap memory before release.

CVE-2026-6327 [MEDIUM] CWE-117 CVE-2026-6327: IBM Concert 1.0.0 through 3.0.0 could allow an unauthorized user to inject data into log messages du IBM Concert 1.0.0 through 3.0.0 could allow an unauthorized user to inject data into log messages due to improper neutralization of special elements when written to log files.

CVE-2025-36159 [MEDIUM] CWE-117 CVE-2025-36159: IBM Concert 1.0.0 through 2.0.0 could allow a local user to forge log files to impersonate other use IBM Concert 1.0.0 through 2.0.0 could allow a local user to forge log files to impersonate other users or hide their identity due to improper neutralization of output.

CVE-2026-1510 [MEDIUM] CWE-244 CVE-2026-1510: IBM Concert 1.0 through 3.0.0 is vulnerable to Information Disclosure via Heap Inspection. IBM Concert 1.0 through 3.0.0 is vulnerable to Information Disclosure via Heap Inspection.

CVE-2024-43180 [MEDIUM] CWE-614 CVE-2024-43180: IBM Concert 1.0 does not set the secure attribute on authorization tokens or session cookies. Attack 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.

CVE-2026-4405 [MEDIUM] CWE-525 CVE-2026-4405: IBM Concert 1.0 through 3.0.0 allows web page cache to be stored locally which can be read by anothe IBM Concert 1.0 through 3.0.0 allows web page cache to be stored locally which can be read by another user on the system.

CVE-2026-6930 [LOW] CWE-327 CVE-2026-6930: IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

CVE-2026-3303 [LOW] CWE-942 CVE-2026-3303: IBM Concert 1.0 through 3.0.0 uses cross-origin resource sharing (CORS) which could allow an attacke IBM Concert 1.0 through 3.0.0 uses cross-origin resource sharing (CORS) which could allow an attacker to carry out privileged actions as the domain name is not being limited to only trusted domains.

CVE-2026-1501 [LOW] CWE-295 CVE-2026-1501: IBM Concert 1.0 through 3.0.0 is vulnerable to Improper Certificate Validation. IBM Concert 1.0 through 3.0.0 is vulnerable to Improper Certificate Validation.

CVE-2024-43173 [LOW] CWE-1275 CVE-2024-43173: IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSi IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute.