IBM Concert vulnerabilities

IBM Concert versions 1.0.0 through 2.1.0 is vulnerable to malicious file upload due to lack of content validation for files uploaded to the web interface. An attacker could exploit this to upload harmful files.

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.

IBM Concert versions 1.0 through 3.0.0 is vulnerable to information disclosure via heap inspection. The flaw may allow leakage of data from application memory.

IBM Concert versions 1.0 through 3.0.0 is vulnerable to improper certificate validation. The application incorrectly verifies certificates, potentially accepting forged or invalid certificates.

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

IBM Concert 1.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. This may lead to manipulation of log content.

IBM Concert versions 1.0.0 through 3.0.0 allow recursive copying of directories without proper controls, which can lead to unintentional inclusion of sensitive or unnecessary files and increased attack surface.

IBM Concert 1.0.0 through 3.0.0 invokes OS commands without fully qualifying executable paths or adequately restricting search path resolution. An attacker with local system access can manipulate the search path environment to execute untrusted or malicious code.

IBM Concert versions 1.0.0 through 3.0.0 allows a remote attacker to traverse directories by sending a crafted URL request containing "dot dot" sequences. This enables viewing arbitrary files on the system.

IBM Concert 1.0.0 through 3.0.0 has a double free vulnerability due to incorrect memory management. A local attacker can exploit this flaw to corrupt heap memory and execute arbitrary code in the context of the affected process.

IBM Concert versions 1.0.0 through 3.0.0 is vulnerable to improper access control, allowing unauthorized modification of application files.

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.

IBM Concert versions 1.0.0 through 3.0.0 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.

IBM Concert does not properly enforce storage limits. A remote authenticated attacker could cause a denial of service as a result.

IBM Concert is vulnerable to server-side request forgery (SSRF). An authenticated attacker may send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

IBM Concert recursively copies build context directories into container images. A local attacker could obtain sensitive information as a result.

IBM Concert uses weaker than expected cryptographic algorithms. An attacker could decrypt highly sensitive information as a result.

IBM Concert versions 1.0.0 through 3.0.0 could allow a remote attacker to cause a denial of service using a specially crafted regular expression that would cause excessive resource consumption.

IBM Concert versions 1.0.0 through 2.3.1 may allow a remote attacker to perform unauthorized actions using man-in-the-middle techniques due to improper certificate validation.

IBM Concert versions 1.0.0 through 2.2.0 creates temporary files with predictable names. A local user can exploit a symlink attack to overwrite arbitrary files.

IBM Concert 1.0.0 through 2.1.0 could allow a local user to escalate their privileges due to a race condition of a symbolic link.

IBM Concert versions 1.0.0 through 2.1.0 could allow a remote attacker to obtain sensitive information from allocated memory due to improper clearing of heap memory.

IBM Concert (versions 1.0.0 through 2.1.0) is vulnerable to a stack-based buffer overflow due to improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.

IBM Concert 1.0.0 through 2.1.0 stores sensitive information in cleartext during recursive docker builds which could be obtained by a local user.

IBM Concert versions 1.0.0 through 2.0.0 use weaker than expected cryptographic algorithms, which could allow an attacker to decrypt highly sensitive information.

IBM Concert versions 1.0.0 through 2.0.0 could disclose sensitive server information from HTTP response headers, which could aid in further attacks against the system.

IBM Concert 1.0.0 through 2.0.0 allows a local user to forge log files to impersonate other users or hide their identity due to improper neutralization of output.

IBM Concert 1.0.0 through 2.0.0 allows a local user with specific permission to obtain sensitive information from files due to uncontrolled recursive directory copying.

IBM Concert versions 1.0.0 through 2.0.0 is vulnerable to cross-site scripting. An unauthenticated attacker can embed arbitrary JavaScript code in the Web UI, altering functionality and potentially leading to credentials disclosure within a trusted session.

IBM Concert 1.0.0 through 2.0.0 could allow a remote attacker to obtain sensitive information due to the failure to properly enable HTTP Strict-Transport-Security. An attacker could exploit this to obtain sensitive information using man-in-the-middle techniques.

IBM Concert 1.0.0 through 2.0.0 Software is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.