Concert vulnerabilities
33 known vulnerabilities in Concert from IBM. 33 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
Concert: Improper Neutralization of Special Elements used in an OS Command
IBM Concert 1.0 through 3.0.1.1 allows an attacker can supply crafted input that is incorporated into an operating system command without adequate validation or sanitization. Successful exploitation allows remote attackers to execute arbitrary commands on the
- 9.8 Critical severity
Concert: Improper Neutralization of Special Elements used in an OS Command
IBM Concert 1.0 through 3.0.1.1 contains components that allow potentially unsafe command execution, which could be exploited to run arbitrary system commands on the host.
- 7.5 High severity
Concert: Use of Insufficiently Random Values
IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 7.5 High severity
Concert: Use of a Broken or Risky Cryptographic Algorithm
IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 7.8 High severity
Concert: Uncontrolled Search Path Element
IBM Concert 1.0.0 through 3.0.0 invokes operating system commands without fully qualifying executable paths or adequately restricting search path resolution. As a result, an attacker with local system access can manipulate the search path environment to execut
- 9.8 Critical severity
Concert: Use After Free
IBM Concert 1.0.0 through 3.0.0 references or accesses memory after it has been freed. This allows an attacker who can influence program execution or input may exploit this condition to corrupt memory, cause application crashes, or execute arbitrary code.
- 7.8 High severity
Concert: Double Free
IBM Concert 1.0.0 through 3.0.0 has a double free vulnerability that exists 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.
- 7.8 High severity
Concert: Buffer Copy without Checking Size of Input
IBM Concert 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.
- 9.8 Critical severity
Concert: Improper Neutralization of Special Elements used in an OS Command
IBM Concert 1.0.0 through 3.0.0 allows an unauthenticated remote attacker can supply specially crafted input that is incorporated into OS commands, resulting in arbitrary command execution on the underlying system. Successful exploitation allows remote code ex
- 9.6 Critical severity
Concert: Improper Privilege Management
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.
- 7.5 High severity
Concert: Use of a Broken or Risky Cryptographic Algorithm
IBM Concert 1.0.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 9.1 Critical severity
Concert: Improper Neutralization of Special Elements used in an SQL Command
IBM Concert 1.0.0 through 2.3.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.
- 7.5 High severity
Concert: Use of a Cryptographic Primitive with a Risky Implementation
IBM Concert 1.0.0 through 2.2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information
- 7.4 High severity
Concert: Incorrect Permission Assignment for Critical Resource
IBM Concert 1.0.0 through 2.1.0 could allow a local user with specific knowledge about the system's architecture to escalate their privileges due to incorrect file permissions for critical resources.
- 9.8 Critical severity
Concert: Use of Hard-coded Credentials
IBM Concert 1.0.0 through 2.1.0 could allow a remote attacker to obtain sensitive information or perform unauthorized actions due to the use of hard coded user credentials.
- 7.5 High severity
Concert: Use of a Broken or Risky Cryptographic Algorithm
IBM Concert 1.0.0 through 2.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 7.5 High severity
Concert: Use of a One-Way Hash without a Salt
IBM Concert 1.0.0 through 2.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 7.5 High severity
Concert: Improper Clearing of Heap Memory Before Release
IBM Concert 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.
- 7.5 High severity
Concert: Improper Clearing of Heap Memory Before Release
IBM Concert 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.
- 7.5 High severity
Concert: Improper Clearing of Heap Memory Before Release
IBM Concert 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.
- 7.8 High severity
Concert: Improper Restriction of Operations within the Bounds of a Memory Buffer
IBM Concert 1.0.0 through 2.1.0 is vulnerable to a stack-based buffer overflow, caused by improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.
- 7.5 High severity
Concert: Use of a Broken or Risky Cryptographic Algorithm
IBM Concert 1.0.0 through 2.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 7.5 High severity
Concert: Exposure of Sensitive System Information to an Unauthorized Control Sphere
IBM Concert 1.0.0 through 2.0.0 could disclose sensitive server information from HTTP response headers that could aid in further attacks against the system.
- 7.5 High severity
Concert Software: Access of Uninitialized Pointer
IBM Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to obtain sensitive information from allocated memory due to improper clearing of heap memory.
- 7.5 High severity
Concert Software: Use of a Broken or Risky Cryptographic Algorithm
IBM Concert Software 1.0.0 through 1.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 7.5 High severity
Concert Software: Use of Hard-coded Credentials
IBM Concert Software 1.0.0 through 1.1.0 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.
- 7.5 High severity
Concert Software: Inefficient Regular Expression Complexity
IBM Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to cause a denial of service using a specially crafted regular expression that would cause excessive resource consumption.
- 9.8 Critical severity
Concert Software: Incorrect Comparison
IBM Concert Software 1.0.0 through 1.1.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.
- 7.5 High severity
Concert Software: Improper Removal of Sensitive Information Before Storage or Transfer
IBM Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to obtain sensitive information from allocated memory due to improper clearing of heap memory.
- 7.5 High severity
Concert Software: Exposure of Sensitive Information Due to Incompatible Policies
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to excessive data exposure, allowing attackers to access sensitive information without proper filtering.
- 7.5 High severity
Concert Software: Exposure of Sensitive System Information to an Unauthorized Control Sphere
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, 1.0.2.1, and 1.0.3 could disclose sensitive system information to an unauthorized actor that could be used in further attacks against the system.
- 9.8 Critical severity
Concert Software: Improper Neutralization of Special Elements used in an SQL Command
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.
- 8.8 High severity
Concert Software: Incorrect User Management
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.