Concert
Monthly
Local privilege escalation in IBM Concert 1.0.0 through 3.0.0 lets an attacker who already holds a low-privileged account on the host execute arbitrary code by manipulating the search path used when Concert spawns operating system commands. Because Concert does not fully qualify the executable paths it invokes, a malicious binary placed earlier in the search order is executed with the privileges of the Concert process. The flaw is scored CVSS 3.1 7.8 HIGH (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and requires local system access plus the ability to influence path resolution; no public exploit code has been identified at time of analysis and this CVE is not in CISA KEV. A vendor patch is available.
Use-after-free in IBM Concert 1.0.0 through 3.0.0 lets an attacker who can influence program input or execution flow corrupt heap memory, crash the application, or potentially hijack control flow for code execution. No public exploit code and no confirmed active exploitation were identified at time of analysis, and IBM has published a vendor fix (advisory node 7288830). The vendor-published vector claims unauthenticated network exploitation at 9.8, but our assessment scores the issue AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H: the practical attack is high-complexity, requires an authenticated position to supply the malicious input, and the specific trigger surface is unconfirmed, so real-world severity is materially lower than the published base score suggests.
Heap memory corruption in IBM Concert 1.0.0 through 3.0.0 lets an attacker who already has low-privileged local access to the host trigger a double free (CWE-415) and, with heap grooming, execute arbitrary code in the context of the affected process. Exploitation is authenticated and local only - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (base 7.8) - with full confidentiality, integrity, and availability impact when successful; no public exploit identified at time of analysis. IBM has published a vendor advisory and patch guidance at https://www.ibm.com/support/pages/node/7288830.
Improper bounds checking in IBM Concert 1.0.0 through 3.0.0 lets a local, authenticated user supply overlong input that overflows a buffer and achieves arbitrary code execution under the privileges of the affected process, matching the assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. IBM's own advisory scores the issue 9.8 with a network/unauthenticated vector (AV:N/AC:L/PR:N/UI:N), but the vendor description explicitly states a 'local user' is required, so realistic exposure is confined to systems where an attacker already has a local account - a foothold-to-full-compromise escalation rather than a pre-authentication remote RCE. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM has published an advisory with a vendor-supplied fix.
Unauthenticated remote code execution in IBM Concert 1.0.0 through 3.0.0 lets any attacker who can reach the service send specially crafted input that is incorporated into operating-system commands, executing arbitrary commands with the privileges of the Concert application. The vulnerability is rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication, no user interaction, and no special conditions are required - only network reachability of an unpatched instance. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, so exploitation appears opportunistic-dependent rather than confirmed in the wild, but IBM has published a vendor fix, so the priority is to patch exposed instances before exploit code or scanning activity emerges.
Improperly scoped role-based access control in IBM Concert 1.0.0 through 3.0.0 lets any authenticated user holding even a low-privileged account read and modify resources outside their granted permissions, because the product's RBAC permission definitions rely on wildcards instead of explicit resource scoping. IBM scores this 9.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N), while our independent assessment rates it 8.8 with Scope:Unchanged, meaning the practical severity is high but below the vendor's critical rating; exploitation still requires a valid account and a reachable Concert instance. No public exploit code has been identified at time of analysis and there is no evidence of active exploitation (not in CISA KEV), but IBM has published a vendor patch at support node 7288830.
SQL injection in IBM Concert versions 1.0.0 through 2.3.1 allows remote attackers to inject specially crafted SQL statements and read, insert, modify, or delete arbitrary data in the back-end database. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) indicates network-reachable, low-complexity exploitation with no authentication or user interaction, yielding high confidentiality and integrity impact. A vendor patch is available; no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
IBM Concert 1.0.0 through 3.0.0 contains a local information disclosure flaw in its recursive directory-copy functionality, where a lack of proper access controls can lead to the unintentional inclusion of sensitive or unnecessary files, increasing the attack surface. The vulnerability requires local access to the host and is modeled as unauthenticated (PR:N) with no user interaction (UI:N), but its impact is bounded to confidentiality loss (C:H) with no integrity or availability impact. No public exploit code has been identified, and the vendor has released a patch via IBM support.
Path traversal in IBM Concert 1.0.0 through 3.0.0 permits unauthenticated remote attackers to read files accessible to the Concert service account by sending crafted URLs containing dot-dot-slash sequences. The flaw has a CVSS 3.1 score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), so impact is limited to confidentiality with no write or code execution. No public exploit code was identified at time of analysis, and IBM has made a patch available.
Improper access control in IBM Concert 1.0.0 through 3.0.0 lets a local attacker who already has access to the host modify application files that should be protected, yielding an integrity-only impact with no data disclosure or denial of service. The vendor CVSS vector is 6.2 with AV:L/PR:N, while the independent assessment rates PR:L because exploiting this flaw in practice typically requires at least a local account or a compromised co-resident process; IBM has released a vendor patch. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS score was supplied. This is a genuine integrity risk but not a top-priority emergency, given the local attack vector and the product's limited deployment.
Log injection in IBM Concert 1.0.0 through 3.0.0 allows an authenticated low-privileged user to insert forged or misleading entries into application log files by supplying input that is written without neutralization of special characters such as CRLF sequences. The vulnerability is a CWE-117 improper output neutralization flaw with only a low integrity impact (C:N/I:L/A:N); it cannot be used to read data, execute code, or cause denial of service, and exploitation requires a valid low-privileged account (PR:L). No public exploit code exists and no active exploitation has been identified at time of analysis, and IBM has released a vendor patch.
IBM Concert 1.0.0 through 3.0.0 can be induced to return detailed technical error messages to a requesting browser, leaking implementation detail to a remote, unauthenticated attacker (CVSS 3.1: AV:N/AC:L/PR:N/UI:N, C:L only, 5.3). Impact is limited to low-sensitivity information disclosure with no integrity or availability effect, so the practical value is reconnaissance for follow-on attacks, and only Concert instances whose web interface is reachable by the attacker are exposed. No public exploit identified at time of analysis, and IBM has published a vendor fix; the issue is a low-priority information-disclosure item rather than a standalone compromise vector.
An authenticated remote user of IBM Concert versions 1.0.0 through 3.0.0 can degrade or deny service availability by driving storage consumption past the limits the product is supposed to enforce. The vulnerability is rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning the attacker needs a valid account and network reachability to the Concert service but no user interaction; the only impacted security property is availability, with no confidentiality or integrity loss. Exploitation requires the improperly enforced storage limits tracked as CWE-400 to be exhausted, so the practical effect is resource exhaustion leading to denial of service. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), and a vendor patch is published, which materially lowers the urgency of this availability-only issue.
Server-side request forgery in IBM Concert 1.0.0 through 3.0.0 allows an attacker who holds valid credentials to make the application issue HTTP requests to URLs of their choosing, which can be used to enumerate internal network services and set up follow-on attacks. The impact is bounded: the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, 6.5 by the vendor) reflects limited confidentiality and integrity loss rather than code execution or arbitrary file read, and exploitation requires a reachable Concert feature that dispatches server-side requests to a user-influenced URL. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (it is not in CISA KEV); IBM has published a fix via its support advisory.
Build-context directories belonging to IBM Concert 1.0.0 through 3.0.0 are recursively copied into produced container images, so any sensitive files sitting in that context (credentials, config files, keys, environment files) are baked into the image layers and disclosed to anyone who can pull the image or read its filesystem. The issue is local in nature (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 6.2): an attacker must already be able to obtain or access the built image, and no authentication or user interaction is involved, but the confidentiality impact on whatever was left in the build context is high, with no integrity or availability effect. There is no confirmed active exploitation (no CISA KEV listing) and no public exploit identified at time of analysis, so this is a genuine but low-urgency information-disclosure hygiene defect that matters most where images are pushed to shared or externally reachable registries.
Uncontrolled resource consumption in IBM Concert 1.0.0 through 3.0.0 allows a remote, unauthenticated attacker to degrade service availability by feeding a specially crafted regular expression through the affected input-processing path, causing excessive CPU and memory consumption. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N, availability impact Low only), no credentials or user interaction are required, but the practical blast radius is bounded: only availability is affected, so expect slowdowns or partial unavailability rather than data compromise or full host takeover, and only on Concert deployments that actually expose the vulnerable input surface to untrusted traffic. No public exploit code has been identified at time of analysis and there is no indication this issue is confirmed actively exploited (CISA KEV); the vendor has published a fix advisory, making this a genuine but low-priority patching item.
IBM Concert 1.0.0 through 3.0.0 uses weaker-than-expected cryptographic algorithms that can expose highly sensitive information to decryption by an attacker who obtains the protected data. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, so no authentication or user interaction is required per the vector, but exploitation is constrained by high attack complexity and the need to acquire ciphertext before breaking the weak cryptography. No public exploit identified at time of analysis and no CISA KEV entry were provided; a vendor patch is available via IBM support node 7288830.
IBM Concert versions 1.0.0 through 2.3.1 expose deployments to man-in-the-middle attacks due to improper TLS certificate validation (CWE-295), enabling remote attackers to intercept and manipulate communications between Concert components. The integrity impact is rated High by IBM's own CVSS scoring, meaning an adversary successfully positioned in the network path can perform unauthorized actions against affected Concert instances. No public exploit code has been identified at time of analysis, and IBM has released a patch via advisory 7285337.
IBM Concert versions 1.0.0 through 2.2.0 create temporary files with predictable names, allowing local unauthenticated attackers to overwrite arbitrary files through symlink attacks. An attacker with local system access can exploit this insecure temporary file handling to modify critical application or system files, achieving high integrity impact. No public exploit code or active exploitation has been confirmed at time of analysis.
Concert versions up to 2.1.0 is affected by incorrect permission assignment for critical resource (CVSS 7.4).
IBM Concert 1.0.0 through 2.1.0 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. [CVSS 5.4 MEDIUM]
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to obtain sensitive information using man in the middle techniques due to improper (CVSS 5.9).
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. [CVSS 6.5 MEDIUM]
IBM Concert 1.0.0 through 2.1.0 for Z hub framework is vulnerable to cross-site scripting. [CVSS 6.1 MEDIUM]
IBM Concert 1.0.0 through 2.1.0 for Z hub component is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. [CVSS 6.5 MEDIUM]
Concert versions up to 2.1.0 is affected by use of a broken or risky cryptographic algorithm (CVSS 5.9).
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to conduct various attacks against the vulnerable system, including cross-site scri (CVSS 6.5).
IBM Concert 1.0.0 through 2.1.0 does not invalidate session after logout which could allow an authenticated user to impersonate another user on the system. [CVSS 6.3 MEDIUM]
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to decrypt highly sensitive information (CVSS 5.9).
Concert versions up to 2.1.0 is affected by unrestricted upload of file with dangerous type (CVSS 8.8).
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to a remote attacker to obtain sensitive information from allocated memory due to i (CVSS 5.9).
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to a remote attacker to obtain sensitive information from allocated memory due to i (CVSS 5.9).
Local privilege escalation in IBM Concert 1.0.0 through 2.1.0 lets an attacker who already has a foothold on the host win a symbolic-link race condition (CWE-367 TOCTOU) against a privileged Concert file operation and gain high-integrity read/write/execute capability as the service account, scored CVSS 7.4 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). The vector is local-only with high attack complexity, so success hinges on precisely timing the symlink swap between the check and the use - often requiring repeated attempts - while no victim interaction is needed. No public exploit identified at time of analysis, there is no CISA KEV listing, and the issue is best treated as a real-but-low-priority local hardening problem pending an IBM fix.
IBM Concert 1.0.0 through 2.1.0 can disclose residual heap memory contents to remote, unauthenticated users because server-side buffers are not properly cleared before release (CWE-244). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) describes a network-reachable, low-complexity, confidentiality-only flaw that requires no credentials or user interaction, but the leak is opportunistic and non-deterministic - an attacker cannot direct which memory contents are returned, and the specific feature, protocol, or endpoint that echoes the leaked memory is not named in the available data. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, so real-world risk is governed largely by whether the affected interface is actually reachable (internal-only deployments and access restrictions materially reduce exposure).
Local code execution in IBM Concert 1.0.0 through 2.1.0 allows an authenticated attacker to overflow a stack buffer and run arbitrary code with the privileges of the vulnerable service. The flaw, caused by improper bounds checking (CWE-119), requires a local account (PR:L) but no victim interaction (UI:N). No public exploit code or active exploitation has been identified at time of analysis.
IBM Concert 1.0.0 through 2.1.0 stores sensitive information - such as credentials and secrets handled during recursive Docker builds - in cleartext on disk, allowing a local user with access to the build host to read and disclose it. The issue is purely a confidentiality exposure (C:H with I:N/A:N, CVSS 6.2) and requires local access to the host where recursive builds run, with PR:N and UI:N in the assessed vector; there is no public exploit identified at time of analysis, and EPSS is very low at 0.10% (1st percentile). Real-world risk is best characterized as low and depends heavily on how many local accounts can reach the build environment and its artifacts.
IBM Concert 1.0.0 through 2.0.0 relies on weaker-than-expected cryptographic algorithms, permitting an attacker who already possesses data encrypted by the product to recover highly sensitive plaintext. Exploitation cannot be initiated by a remote network request against a default deployment: the attacker must first obtain the protected ciphertext through on-path interception, access to encrypted data at rest, or a prior compromise, which makes the vulnerability a weakness-amplifier rather than a standalone entry point. The CVSS base score is 7.5 (High) with a network vector, but the independent assessment raises attack complexity to High and the EPSS score is 0.02% (6th percentile), with no public exploit code and no CISA KEV listing - indicating a low-priority, low-real-risk issue in practice. Impact is limited to confidentiality.
IBM Concert Software 1.0.0 through 2.0.0 could allow a remote attacker to hijack the clicking action of the victim. Rated medium severity (CVSS 6.3), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 6.2), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 through 2.0.0 could allow a local user with specific permission to obtain sensitive information from files due to uncontrolled recursive directory copying. Rated medium severity (CVSS 5.1), this vulnerability is no authentication required. No vendor patch available.
IBM Concert 1.0.0 through 2.0.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 through 2.0.0 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict-Transport-Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
Server-side request forgery in IBM Concert 1.0.0 through 2.0.0 allows an authenticated user who can reach a URL-fetching feature to make the server issue requests to attacker-chosen destinations, enabling internal network enumeration and access to services or cloud metadata endpoints reachable from the Concert host's network position. The flaw (CWE-918, CVSS 5.4, vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) requires a valid low-privileged account and no user interaction, and its impact is bounded by what the server itself can reach. No public exploit code has been identified at time of analysis and EPSS is only 0.16% (5th percentile), so this is not a confirmed-actively-exploited issue and represents low real-world priority.
Information disclosure in IBM Concert Software 1.0.0 through 2.0.0 allows an authenticated local user to read sensitive data that the application leaves behind in heap buffers it frees without first clearing (CWE-244). Exploitation is confined to the local host and requires low privileges (CVSS 3.1 AV:L/AC:L/PR:L, medium 5.5, confidentiality-only impact), and because the attacker cannot control which residual data happens to remain in freed memory, any leak is opportunistic rather than deterministic. No public exploit code is identified, the issue is not in CISA KEV, and EPSS is negligible at 0.12% (1st percentile), so this rates as a genuinely low-priority finding despite the medium base score.
Improper neutralization of log input in IBM Concert versions 1.0.0 through 2.0.0 allows a remote attacker to forge, spoof, or corrupt system log entries by injecting newline/CRLF or control characters into application input fields that are written verbatim into system logs. The flaw is network-reachable with low attack complexity and requires no user interaction per the assessed CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), and the impact is confined to log integrity - no data confidentiality or availability loss. Overall risk is low: EPSS is only 0.22% (11th percentile), no public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV, so this is an audit-integrity nuisance rather than a code-execution or data-theft primitive.
IBM Concert Software versions 1.0.0 through 1.1.0 fail to properly clear heap memory before reusing it, allowing a remote, unauthenticated attacker to read residual data left behind by prior allocations. The weakness is a memory-handling defect (CWE-824) reachable over the network with no authentication or user interaction per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), though the leak is opportunistic - an attacker receives whatever happens to be in the reused buffer rather than a chosen secret, which is why the assessed confidentiality impact is Low rather than the 7.5 High-integrity NVD score. Exploitation signals are weak: EPSS is 0.03% (10th percentile), the issue is not listed in CISA KEV, and no public exploit code has been identified at time of analysis, so real-world priority is low and exposure mainly depends on whether a Concert instance is reachable by untrusted networks.
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. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to perform unauthorized actions using man in the middle techniques due to improper certificate validation. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 6.2), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
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. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
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. Rated low severity (CVSS 3.7), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 could allow a remote attacker to traverse directories on the system. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 is vulnerable to server-side request forgery (SSRF). Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 could allow an authenticated user to cause a denial of service due to the expansion of archive files without controlling resource consumption. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 and 1.0.1 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert 1.0.0, 1.0.1, and 1.0.2 is vulnerable to sensitive information disclosure through specially crafted API Calls. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, 1.0.2.1, and 1.0.3 could allow an authenticated user to inject malicious information or obtain information from log files due to improper log neutralization. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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, caused by the failure to properly enable HTTP Strict Transport Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 is vulnerable to SQL injection. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.1 is vulnerable to cross-site scripting. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute. Rated low severity (CVSS 3.7), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert 1.0 does not set the secure attribute on authorization tokens or session cookies. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Local privilege escalation in IBM Concert 1.0.0 through 3.0.0 lets an attacker who already holds a low-privileged account on the host execute arbitrary code by manipulating the search path used when Concert spawns operating system commands. Because Concert does not fully qualify the executable paths it invokes, a malicious binary placed earlier in the search order is executed with the privileges of the Concert process. The flaw is scored CVSS 3.1 7.8 HIGH (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and requires local system access plus the ability to influence path resolution; no public exploit code has been identified at time of analysis and this CVE is not in CISA KEV. A vendor patch is available.
Use-after-free in IBM Concert 1.0.0 through 3.0.0 lets an attacker who can influence program input or execution flow corrupt heap memory, crash the application, or potentially hijack control flow for code execution. No public exploit code and no confirmed active exploitation were identified at time of analysis, and IBM has published a vendor fix (advisory node 7288830). The vendor-published vector claims unauthenticated network exploitation at 9.8, but our assessment scores the issue AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H: the practical attack is high-complexity, requires an authenticated position to supply the malicious input, and the specific trigger surface is unconfirmed, so real-world severity is materially lower than the published base score suggests.
Heap memory corruption in IBM Concert 1.0.0 through 3.0.0 lets an attacker who already has low-privileged local access to the host trigger a double free (CWE-415) and, with heap grooming, execute arbitrary code in the context of the affected process. Exploitation is authenticated and local only - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (base 7.8) - with full confidentiality, integrity, and availability impact when successful; no public exploit identified at time of analysis. IBM has published a vendor advisory and patch guidance at https://www.ibm.com/support/pages/node/7288830.
Improper bounds checking in IBM Concert 1.0.0 through 3.0.0 lets a local, authenticated user supply overlong input that overflows a buffer and achieves arbitrary code execution under the privileges of the affected process, matching the assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. IBM's own advisory scores the issue 9.8 with a network/unauthenticated vector (AV:N/AC:L/PR:N/UI:N), but the vendor description explicitly states a 'local user' is required, so realistic exposure is confined to systems where an attacker already has a local account - a foothold-to-full-compromise escalation rather than a pre-authentication remote RCE. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM has published an advisory with a vendor-supplied fix.
Unauthenticated remote code execution in IBM Concert 1.0.0 through 3.0.0 lets any attacker who can reach the service send specially crafted input that is incorporated into operating-system commands, executing arbitrary commands with the privileges of the Concert application. The vulnerability is rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication, no user interaction, and no special conditions are required - only network reachability of an unpatched instance. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, so exploitation appears opportunistic-dependent rather than confirmed in the wild, but IBM has published a vendor fix, so the priority is to patch exposed instances before exploit code or scanning activity emerges.
Improperly scoped role-based access control in IBM Concert 1.0.0 through 3.0.0 lets any authenticated user holding even a low-privileged account read and modify resources outside their granted permissions, because the product's RBAC permission definitions rely on wildcards instead of explicit resource scoping. IBM scores this 9.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N), while our independent assessment rates it 8.8 with Scope:Unchanged, meaning the practical severity is high but below the vendor's critical rating; exploitation still requires a valid account and a reachable Concert instance. No public exploit code has been identified at time of analysis and there is no evidence of active exploitation (not in CISA KEV), but IBM has published a vendor patch at support node 7288830.
SQL injection in IBM Concert versions 1.0.0 through 2.3.1 allows remote attackers to inject specially crafted SQL statements and read, insert, modify, or delete arbitrary data in the back-end database. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) indicates network-reachable, low-complexity exploitation with no authentication or user interaction, yielding high confidentiality and integrity impact. A vendor patch is available; no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
IBM Concert 1.0.0 through 3.0.0 contains a local information disclosure flaw in its recursive directory-copy functionality, where a lack of proper access controls can lead to the unintentional inclusion of sensitive or unnecessary files, increasing the attack surface. The vulnerability requires local access to the host and is modeled as unauthenticated (PR:N) with no user interaction (UI:N), but its impact is bounded to confidentiality loss (C:H) with no integrity or availability impact. No public exploit code has been identified, and the vendor has released a patch via IBM support.
Path traversal in IBM Concert 1.0.0 through 3.0.0 permits unauthenticated remote attackers to read files accessible to the Concert service account by sending crafted URLs containing dot-dot-slash sequences. The flaw has a CVSS 3.1 score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), so impact is limited to confidentiality with no write or code execution. No public exploit code was identified at time of analysis, and IBM has made a patch available.
Improper access control in IBM Concert 1.0.0 through 3.0.0 lets a local attacker who already has access to the host modify application files that should be protected, yielding an integrity-only impact with no data disclosure or denial of service. The vendor CVSS vector is 6.2 with AV:L/PR:N, while the independent assessment rates PR:L because exploiting this flaw in practice typically requires at least a local account or a compromised co-resident process; IBM has released a vendor patch. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS score was supplied. This is a genuine integrity risk but not a top-priority emergency, given the local attack vector and the product's limited deployment.
Log injection in IBM Concert 1.0.0 through 3.0.0 allows an authenticated low-privileged user to insert forged or misleading entries into application log files by supplying input that is written without neutralization of special characters such as CRLF sequences. The vulnerability is a CWE-117 improper output neutralization flaw with only a low integrity impact (C:N/I:L/A:N); it cannot be used to read data, execute code, or cause denial of service, and exploitation requires a valid low-privileged account (PR:L). No public exploit code exists and no active exploitation has been identified at time of analysis, and IBM has released a vendor patch.
IBM Concert 1.0.0 through 3.0.0 can be induced to return detailed technical error messages to a requesting browser, leaking implementation detail to a remote, unauthenticated attacker (CVSS 3.1: AV:N/AC:L/PR:N/UI:N, C:L only, 5.3). Impact is limited to low-sensitivity information disclosure with no integrity or availability effect, so the practical value is reconnaissance for follow-on attacks, and only Concert instances whose web interface is reachable by the attacker are exposed. No public exploit identified at time of analysis, and IBM has published a vendor fix; the issue is a low-priority information-disclosure item rather than a standalone compromise vector.
An authenticated remote user of IBM Concert versions 1.0.0 through 3.0.0 can degrade or deny service availability by driving storage consumption past the limits the product is supposed to enforce. The vulnerability is rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning the attacker needs a valid account and network reachability to the Concert service but no user interaction; the only impacted security property is availability, with no confidentiality or integrity loss. Exploitation requires the improperly enforced storage limits tracked as CWE-400 to be exhausted, so the practical effect is resource exhaustion leading to denial of service. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), and a vendor patch is published, which materially lowers the urgency of this availability-only issue.
Server-side request forgery in IBM Concert 1.0.0 through 3.0.0 allows an attacker who holds valid credentials to make the application issue HTTP requests to URLs of their choosing, which can be used to enumerate internal network services and set up follow-on attacks. The impact is bounded: the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, 6.5 by the vendor) reflects limited confidentiality and integrity loss rather than code execution or arbitrary file read, and exploitation requires a reachable Concert feature that dispatches server-side requests to a user-influenced URL. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (it is not in CISA KEV); IBM has published a fix via its support advisory.
Build-context directories belonging to IBM Concert 1.0.0 through 3.0.0 are recursively copied into produced container images, so any sensitive files sitting in that context (credentials, config files, keys, environment files) are baked into the image layers and disclosed to anyone who can pull the image or read its filesystem. The issue is local in nature (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 6.2): an attacker must already be able to obtain or access the built image, and no authentication or user interaction is involved, but the confidentiality impact on whatever was left in the build context is high, with no integrity or availability effect. There is no confirmed active exploitation (no CISA KEV listing) and no public exploit identified at time of analysis, so this is a genuine but low-urgency information-disclosure hygiene defect that matters most where images are pushed to shared or externally reachable registries.
Uncontrolled resource consumption in IBM Concert 1.0.0 through 3.0.0 allows a remote, unauthenticated attacker to degrade service availability by feeding a specially crafted regular expression through the affected input-processing path, causing excessive CPU and memory consumption. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N, availability impact Low only), no credentials or user interaction are required, but the practical blast radius is bounded: only availability is affected, so expect slowdowns or partial unavailability rather than data compromise or full host takeover, and only on Concert deployments that actually expose the vulnerable input surface to untrusted traffic. No public exploit code has been identified at time of analysis and there is no indication this issue is confirmed actively exploited (CISA KEV); the vendor has published a fix advisory, making this a genuine but low-priority patching item.
IBM Concert 1.0.0 through 3.0.0 uses weaker-than-expected cryptographic algorithms that can expose highly sensitive information to decryption by an attacker who obtains the protected data. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, so no authentication or user interaction is required per the vector, but exploitation is constrained by high attack complexity and the need to acquire ciphertext before breaking the weak cryptography. No public exploit identified at time of analysis and no CISA KEV entry were provided; a vendor patch is available via IBM support node 7288830.
IBM Concert versions 1.0.0 through 2.3.1 expose deployments to man-in-the-middle attacks due to improper TLS certificate validation (CWE-295), enabling remote attackers to intercept and manipulate communications between Concert components. The integrity impact is rated High by IBM's own CVSS scoring, meaning an adversary successfully positioned in the network path can perform unauthorized actions against affected Concert instances. No public exploit code has been identified at time of analysis, and IBM has released a patch via advisory 7285337.
IBM Concert versions 1.0.0 through 2.2.0 create temporary files with predictable names, allowing local unauthenticated attackers to overwrite arbitrary files through symlink attacks. An attacker with local system access can exploit this insecure temporary file handling to modify critical application or system files, achieving high integrity impact. No public exploit code or active exploitation has been confirmed at time of analysis.
Concert versions up to 2.1.0 is affected by incorrect permission assignment for critical resource (CVSS 7.4).
IBM Concert 1.0.0 through 2.1.0 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. [CVSS 5.4 MEDIUM]
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to obtain sensitive information using man in the middle techniques due to improper (CVSS 5.9).
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. [CVSS 6.5 MEDIUM]
IBM Concert 1.0.0 through 2.1.0 for Z hub framework is vulnerable to cross-site scripting. [CVSS 6.1 MEDIUM]
IBM Concert 1.0.0 through 2.1.0 for Z hub component is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. [CVSS 6.5 MEDIUM]
Concert versions up to 2.1.0 is affected by use of a broken or risky cryptographic algorithm (CVSS 5.9).
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to conduct various attacks against the vulnerable system, including cross-site scri (CVSS 6.5).
IBM Concert 1.0.0 through 2.1.0 does not invalidate session after logout which could allow an authenticated user to impersonate another user on the system. [CVSS 6.3 MEDIUM]
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to decrypt highly sensitive information (CVSS 5.9).
Concert versions up to 2.1.0 is affected by unrestricted upload of file with dangerous type (CVSS 8.8).
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to a remote attacker to obtain sensitive information from allocated memory due to i (CVSS 5.9).
Concert versions up to 2.1.0 contains a vulnerability that allows attackers to a remote attacker to obtain sensitive information from allocated memory due to i (CVSS 5.9).
Local privilege escalation in IBM Concert 1.0.0 through 2.1.0 lets an attacker who already has a foothold on the host win a symbolic-link race condition (CWE-367 TOCTOU) against a privileged Concert file operation and gain high-integrity read/write/execute capability as the service account, scored CVSS 7.4 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). The vector is local-only with high attack complexity, so success hinges on precisely timing the symlink swap between the check and the use - often requiring repeated attempts - while no victim interaction is needed. No public exploit identified at time of analysis, there is no CISA KEV listing, and the issue is best treated as a real-but-low-priority local hardening problem pending an IBM fix.
IBM Concert 1.0.0 through 2.1.0 can disclose residual heap memory contents to remote, unauthenticated users because server-side buffers are not properly cleared before release (CWE-244). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) describes a network-reachable, low-complexity, confidentiality-only flaw that requires no credentials or user interaction, but the leak is opportunistic and non-deterministic - an attacker cannot direct which memory contents are returned, and the specific feature, protocol, or endpoint that echoes the leaked memory is not named in the available data. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, so real-world risk is governed largely by whether the affected interface is actually reachable (internal-only deployments and access restrictions materially reduce exposure).
Local code execution in IBM Concert 1.0.0 through 2.1.0 allows an authenticated attacker to overflow a stack buffer and run arbitrary code with the privileges of the vulnerable service. The flaw, caused by improper bounds checking (CWE-119), requires a local account (PR:L) but no victim interaction (UI:N). No public exploit code or active exploitation has been identified at time of analysis.
IBM Concert 1.0.0 through 2.1.0 stores sensitive information - such as credentials and secrets handled during recursive Docker builds - in cleartext on disk, allowing a local user with access to the build host to read and disclose it. The issue is purely a confidentiality exposure (C:H with I:N/A:N, CVSS 6.2) and requires local access to the host where recursive builds run, with PR:N and UI:N in the assessed vector; there is no public exploit identified at time of analysis, and EPSS is very low at 0.10% (1st percentile). Real-world risk is best characterized as low and depends heavily on how many local accounts can reach the build environment and its artifacts.
IBM Concert 1.0.0 through 2.0.0 relies on weaker-than-expected cryptographic algorithms, permitting an attacker who already possesses data encrypted by the product to recover highly sensitive plaintext. Exploitation cannot be initiated by a remote network request against a default deployment: the attacker must first obtain the protected ciphertext through on-path interception, access to encrypted data at rest, or a prior compromise, which makes the vulnerability a weakness-amplifier rather than a standalone entry point. The CVSS base score is 7.5 (High) with a network vector, but the independent assessment raises attack complexity to High and the EPSS score is 0.02% (6th percentile), with no public exploit code and no CISA KEV listing - indicating a low-priority, low-real-risk issue in practice. Impact is limited to confidentiality.
IBM Concert Software 1.0.0 through 2.0.0 could allow a remote attacker to hijack the clicking action of the victim. Rated medium severity (CVSS 6.3), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 6.2), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 through 2.0.0 could allow a local user with specific permission to obtain sensitive information from files due to uncontrolled recursive directory copying. Rated medium severity (CVSS 5.1), this vulnerability is no authentication required. No vendor patch available.
IBM Concert 1.0.0 through 2.0.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 through 2.0.0 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict-Transport-Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
Server-side request forgery in IBM Concert 1.0.0 through 2.0.0 allows an authenticated user who can reach a URL-fetching feature to make the server issue requests to attacker-chosen destinations, enabling internal network enumeration and access to services or cloud metadata endpoints reachable from the Concert host's network position. The flaw (CWE-918, CVSS 5.4, vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) requires a valid low-privileged account and no user interaction, and its impact is bounded by what the server itself can reach. No public exploit code has been identified at time of analysis and EPSS is only 0.16% (5th percentile), so this is not a confirmed-actively-exploited issue and represents low real-world priority.
Information disclosure in IBM Concert Software 1.0.0 through 2.0.0 allows an authenticated local user to read sensitive data that the application leaves behind in heap buffers it frees without first clearing (CWE-244). Exploitation is confined to the local host and requires low privileges (CVSS 3.1 AV:L/AC:L/PR:L, medium 5.5, confidentiality-only impact), and because the attacker cannot control which residual data happens to remain in freed memory, any leak is opportunistic rather than deterministic. No public exploit code is identified, the issue is not in CISA KEV, and EPSS is negligible at 0.12% (1st percentile), so this rates as a genuinely low-priority finding despite the medium base score.
Improper neutralization of log input in IBM Concert versions 1.0.0 through 2.0.0 allows a remote attacker to forge, spoof, or corrupt system log entries by injecting newline/CRLF or control characters into application input fields that are written verbatim into system logs. The flaw is network-reachable with low attack complexity and requires no user interaction per the assessed CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), and the impact is confined to log integrity - no data confidentiality or availability loss. Overall risk is low: EPSS is only 0.22% (11th percentile), no public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV, so this is an audit-integrity nuisance rather than a code-execution or data-theft primitive.
IBM Concert Software versions 1.0.0 through 1.1.0 fail to properly clear heap memory before reusing it, allowing a remote, unauthenticated attacker to read residual data left behind by prior allocations. The weakness is a memory-handling defect (CWE-824) reachable over the network with no authentication or user interaction per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), though the leak is opportunistic - an attacker receives whatever happens to be in the reused buffer rather than a chosen secret, which is why the assessed confidentiality impact is Low rather than the 7.5 High-integrity NVD score. Exploitation signals are weak: EPSS is 0.03% (10th percentile), the issue is not listed in CISA KEV, and no public exploit code has been identified at time of analysis, so real-world priority is low and exposure mainly depends on whether a Concert instance is reachable by untrusted networks.
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. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to perform unauthorized actions using man in the middle techniques due to improper certificate validation. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to cross-site scripting. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 6.2), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
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. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
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. Rated low severity (CVSS 3.7), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 could allow a remote attacker to traverse directories on the system. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 is vulnerable to server-side request forgery (SSRF). Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.5 could allow an authenticated user to cause a denial of service due to the expansion of archive files without controlling resource consumption. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0 and 1.0.1 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert 1.0.0, 1.0.1, and 1.0.2 is vulnerable to sensitive information disclosure through specially crafted API Calls. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, 1.0.2.1, and 1.0.3 could allow an authenticated user to inject malicious information or obtain information from log files due to improper log neutralization. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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, caused by the failure to properly enable HTTP Strict Transport Security. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 is vulnerable to SQL injection. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
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. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert Software 1.0.0 through 1.0.1 is vulnerable to cross-site scripting. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute. Rated low severity (CVSS 3.7), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
IBM Concert 1.0 does not set the secure attribute on authorization tokens or session cookies. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.