CVE-2025-33015

IBM Concert versions 1.0.0 through 3.0.0 references or accesses memory after it has been freed (use-after-free). An attacker who can influence program execution or input may exploit this condition to corrupt memory, cause application crashes, or execute arbitrary code.

IBM Concert versions 1.0.0 through 3.0.0 is vulnerable to a buffer overflow caused by improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.

IBM Concert versions 1.0.0 through 3.0.0 allows an unauthenticated remote attacker to supply specially crafted input that is incorporated into OS commands, resulting in arbitrary command execution. Successful exploitation allows remote code execution with the privileges of the affected application.

IBM Concert 1.0.0 through 3.0.0 could allow a remote authenticated attacker to access or modify unauthorized resources due to the use of wildcards in RBAC permission definitions.

IBM Concert versions 1.0.0 through 2.3.1 are vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, potentially allowing viewing, adding, modifying, or deleting information in the back-end database.

IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms. This could allow an attacker to decrypt highly sensitive information.

IBM Concert 1.0 through 3.0.0 is vulnerable to cross-site scripting. This allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI, altering intended functionality and potentially leading to credential disclosure within a trusted session.

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.

IBM Concert 1.0 through 3.0.0 allows information disclosure through exposure of schema suggestions.

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 limited to only trusted domains.