Concert
by IBM
CVEs (66)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-13044 | Med | 0.40 | 6.2 | 0.00 | Apr 7, 2026 | IBM Concert 1.0.0 through 2.2.0 creates temporary files with predictable names, which allows local users to overwrite arbitrary files via a symlink attack. | ||
| CVE-2025-64648 | 0.00 | — | 0.00 | Mar 25, 2026 | IBM Concert 1.0.0 through 2.2.0 transmits data in clear text that could allow an attacker to obtain sensitive information using man in the middle techniques. | |||
| CVE-2025-64647 | 0.00 | — | 0.00 | Mar 25, 2026 | 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 | |||
| CVE-2025-64646 | 0.00 | — | 0.00 | Mar 25, 2026 | IBM Concert 1.0.0 through 2.2.0 could allow an attacker to access sensitive information in memory due to the buffer not properly clearing resources. | |||
| CVE-2025-36440 | 0.00 | — | 0.00 | Mar 25, 2026 | IBM Concert 1.0.0 through 2.2.0 could allow a local user to obtain sensitive information due to missing function level access control. | |||
| CVE-2025-36438 | 0.00 | — | 0.00 | Mar 25, 2026 | 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-2025-12708 | 0.00 | — | 0.00 | Mar 25, 2026 | IBM Concert 1.0.0 through 2.2.0 contains hard-coded credentials that could be obtained by a local user. | |||
| CVE-2025-33088 | 0.00 | — | 0.00 | Feb 17, 2026 | 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. | |||
| CVE-2025-33101 | 0.00 | — | 0.00 | Feb 17, 2026 | IBM Concert 1.0.0 through 2.1.0 could allow an attacker to obtain sensitive information using man in the middle techniques due to improper clearing of heap memory. | |||
| CVE-2025-33089 | 0.00 | — | 0.00 | Feb 17, 2026 | 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. | |||
| CVE-2025-36243 | 0.00 | — | 0.00 | Feb 17, 2026 | 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. | |||
| CVE-2024-43178 | 0.00 | — | 0.00 | Feb 17, 2026 | 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. | |||
| CVE-2025-36018 | 0.00 | — | 0.00 | Feb 17, 2026 | 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. | |||
| CVE-2025-36019 | 0.00 | — | 0.00 | Feb 17, 2026 | IBM Concert 1.0.0 through 2.1.0 for Z hub framework is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials… | |||
| CVE-2024-51451 | 0.00 | — | 0.00 | Feb 4, 2026 | IBM Concert 1.0.0 through 2.1.0 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session… | |||
| CVE-2024-43181 | 0.00 | — | 0.00 | Feb 4, 2026 | 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. | |||
| CVE-2025-33081 | 0.00 | — | 0.00 | Feb 3, 2026 | IBM Concert 1.0.0 through 2.1.0 stores potentially sensitive information in log files that could be read by a local user. | |||
| CVE-2025-36253 | 0.00 | — | 0.00 | Feb 2, 2026 | 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. | |||
| CVE-2025-33015 | 0.00 | — | 0.00 | Jan 20, 2026 | IBM Concert 1.0.0 through 2.1.0 is vulnerable to malicious file upload by not validating the content of the file uploaded to the web interface. | |||
| CVE-2025-1722 | 0.00 | — | 0.00 | Jan 20, 2026 | 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. |
- risk 0.40cvss 6.2epss 0.00
IBM Concert 1.0.0 through 2.2.0 creates temporary files with predictable names, which allows local users to overwrite arbitrary files via a symlink attack.
- CVE-2025-64648Mar 25, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.2.0 transmits data in clear text that could allow an attacker to obtain sensitive information using man in the middle techniques.
- CVE-2025-64647Mar 25, 2026risk 0.00cvss —epss 0.00
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
- CVE-2025-64646Mar 25, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.2.0 could allow an attacker to access sensitive information in memory due to the buffer not properly clearing resources.
- CVE-2025-36440Mar 25, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.2.0 could allow a local user to obtain sensitive information due to missing function level access control.
- CVE-2025-36438Mar 25, 2026risk 0.00cvss —epss 0.00
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-2025-12708Mar 25, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.2.0 contains hard-coded credentials that could be obtained by a local user.
- CVE-2025-33088Feb 17, 2026risk 0.00cvss —epss 0.00
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.
- CVE-2025-33101Feb 17, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.1.0 could allow an attacker to obtain sensitive information using man in the middle techniques due to improper clearing of heap memory.
- CVE-2025-33089Feb 17, 2026risk 0.00cvss —epss 0.00
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.
- CVE-2025-36243Feb 17, 2026risk 0.00cvss —epss 0.00
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.
- CVE-2024-43178Feb 17, 2026risk 0.00cvss —epss 0.00
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.
- CVE-2025-36018Feb 17, 2026risk 0.00cvss —epss 0.00
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.
- CVE-2025-36019Feb 17, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.1.0 for Z hub framework is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials…
- CVE-2024-51451Feb 4, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.1.0 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session…
- CVE-2024-43181Feb 4, 2026risk 0.00cvss —epss 0.00
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.
- CVE-2025-33081Feb 3, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.1.0 stores potentially sensitive information in log files that could be read by a local user.
- CVE-2025-36253Feb 2, 2026risk 0.00cvss —epss 0.00
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.
- CVE-2025-33015Jan 20, 2026risk 0.00cvss —epss 0.00
IBM Concert 1.0.0 through 2.1.0 is vulnerable to malicious file upload by not validating the content of the file uploaded to the web interface.
- CVE-2025-1722Jan 20, 2026risk 0.00cvss —epss 0.00
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.
Page 1 of 4