This page lists publicly disclosed CVE vulnerabilities affecting ibm powersc (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2023-50962 | IBM PowerSC 1.3, 2.0, and 2.1 MFA does not implement the "HTTP Strict Transport Security" (HSTS) web security policy mechanism. IBM X-Force ID: 276004. | [email protected] | 5.9 | 0.03% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50941 | IBM PowerSC 1.3, 2.0, and 2.1 does not provide logout functionality, which could allow an authenticated user to gain access to an unauthorized user using session fixation. IBM X-Force ID: 275131. | [email protected] | 6.3 | 0.03% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50938 | IBM PowerSC 1.3, 2.0, and 2.1 could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions and possibly launch further attacks against the victim. IBM X-Force ID: 275128. | [email protected] | 6.5 | 0.03% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50935 | IBM PowerSC 1.3, 2.0, and 2.1 fails to properly restrict access to a URL or resource, which may allow a remote attacker to obtain unauthorized access to application functionality and/or resources. IBM X-Force ID: 275115. | [email protected] | 6.5 | 0.04% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50934 | IBM PowerSC 1.3, 2.0, and 2.1 uses single-factor authentication which can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme. IBM X-Force ID: 275114. | [email protected] | 5.3 | 0.04% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50328 | IBM PowerSC 1.3, 2.0, and 2.1 may allow a remote attacker to view session identifiers passed via URL query strings. IBM X-Force ID: 275110. | [email protected] | 3.7 | 0.06% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50940 | IBM PowerSC 1.3, 2.0, and 2.1 uses Cross-Origin Resource Sharing (CORS) which could allow an attacker to carry out privileged actions and retrieve sensitive information as the domain name is not being limited to only trusted domains. IBM X-Force ID: 275130. | [email protected] | 5.3 | 0.04% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50937 | IBM PowerSC 1.3, 2.0, and 2.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 275117. | [email protected] | 5.9 | 0.03% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50936 | IBM PowerSC 1.3, 2.0, and 2.1 does not invalidate session after logout which could allow an authenticated user to impersonate another user on the system. IBM X-Force ID: 275116. | [email protected] | 6.3 | 0.02% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50933 | IBM PowerSC 1.3, 2.0, and 2.1 is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site. IBM X-Force ID: 275113. | [email protected] | 6.1 | 0.09% | 2024-02-02 | 2025-06-03 |
| CVE-2023-50327 | IBM PowerSC 1.3, 2.0, and 2.1 uses insecure HTTP methods which could allow a remote attacker to perform unauthorized file request modification. IBM X-Force ID: 275109. | [email protected] | 5.3 | 0.06% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50326 | IBM PowerSC 1.3, 2.0, and 2.1 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials. IBM X-Force ID: 275107. | [email protected] | 7.5 | 0.04% | 2024-02-02 | 2024-11-21 |
| CVE-2023-50939 | IBM PowerSC 1.3, 2.0, and 2.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 275129. | [email protected] | 5.9 | 0.03% | 2024-02-02 | 2024-11-21 |