Ibm Db2 Mirror For I vulnerabilities
4 known vulnerabilities affecting ibm/db2_mirror_for_i.
Total CVEs
4
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
MEDIUM4
Vulnerabilities
Page 1 of 1
CVE-2025-36117MEDIUMCVSS 6.3v7.4v7.5+2 more2025-07-23
CVE-2025-36117 [MEDIUM] CWE-384 CVE-2025-36117: IBM Db2 Mirror for i 7.4, 7.5, and 7.6 does not disallow the session id after use which could allow
IBM Db2 Mirror for i 7.4, 7.5, and 7.6 does not disallow the session id after use which could allow an authenticated user to impersonate another user on the system.
cvelistv5nvd
CVE-2025-36116MEDIUMCVSS 6.3v7.4v7.5+2 more2025-07-23
CVE-2025-36116 [MEDIUM] CWE-1385 CVE-2025-36116: IBM Db2 Mirror for i 7.4, 7.5, and 7.6 GUI is affected by cross-site WebSocket hijacking vulnerabili
IBM Db2 Mirror for i 7.4, 7.5, and 7.6 GUI is affected by cross-site WebSocket hijacking vulnerability. By sending a specially crafted request, an unauthenticated malicious actor could exploit this vulnerability to sniff an existing WebSocket connection to then remotely perform operations that the user is not allowed to perform.
cvelistv5nvd
CVE-2023-47741MEDIUMCVSS 5.3v7.4v7.5+1 more2023-12-18
CVE-2023-47741 [MEDIUM] CWE-522 CVE-2023-47741:
IBM i 7.3, 7.4, 7.5, IBM i Db2 Mirror for i 7.4 and 7.5 web browser clients may leave clear-text pa
IBM i 7.3, 7.4, 7.5, IBM i Db2 Mirror for i 7.4 and 7.5 web browser clients may leave clear-text passwords in browser memory that can be viewed using common browser tools before the memory is garbage collected. A malicious actor with access to the victim's PC could exploit this vulnerability to gain access to the IBM i operating system. IBM X-Force
cvelistv5nvd
CVE-2022-43928MEDIUMCVSS 6.5v7.4v7.5+1 more2023-04-07
CVE-2022-43928 [MEDIUM] CVE-2022-43928: The IBM Toolbox for Java (Db2 Mirror for i 7.4 and 7.5) could allow a user to obtain sensitive infor
The IBM Toolbox for Java (Db2 Mirror for i 7.4 and 7.5) could allow a user to obtain sensitive information, caused by utilizing a Java string for processing. Since Java strings are immutable, their contents exist in memory until garbage collected. This means sensitive data could be visible in memory over an indefinite amount of time. IBM has addressed this
cvelistv5nvd