Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Sterling_secure_proxy
(Ibm)| Repositories |
Unknown: This might be proprietary software. |
| #Vulnerabilities | 29 |
| Date | Id | Summary | Products | Score | Patch | Annotated |
|---|---|---|---|---|---|---|
| 2022-02-23 | CVE-2022-22336 | IBM Sterling External Authentication Server and IBM Sterling Secure Proxy 6.0.3.0, 6.0.2.0, and 3.4.3.2 could allow a remote user to consume resources causing a denial of service due to a resource leak. IBM X-Force ID: 219395. | Sterling_external_authentication_server, Sterling_secure_proxy | 7.5 | ||
| 2022-05-17 | CVE-2021-29726 | IBM Sterling Secure Proxy 6.0.3 and IBM Secure External Authentication Server 6.0.3 does not properly ensure that a certificate is actually associated with the host due to improper validation of certificates. IBM X-Force ID: 201104. | Secure_external_authentication_server, Sterling_secure_proxy | 5.3 | ||
| 2022-12-06 | CVE-2022-34361 | IBM Sterling Secure Proxy 6.0.3 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 230522. | Sterling_secure_proxy | 7.5 | ||
| 2023-02-08 | CVE-2022-34362 | IBM Sterling Secure Proxy 6.0.3 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 hijacking. IBM X-Force ID: 230523. | Sterling_secure_proxy | 4.6 | ||
| 2023-02-08 | CVE-2022-35720 | IBM Sterling External Authentication Server 6.1.0 and IBM Sterling Secure Proxy 6.0.3 uses weaker than expected cryptographic algorithms during installation that could allow a local attacker to decrypt sensitive information. IBM X-Force ID: 231373. | Sterling_external_authentication_server, Sterling_secure_proxy | 5.5 | ||
| 2023-09-05 | CVE-2023-32338 | IBM Sterling Secure Proxy and IBM Sterling External Authentication Server 6.0.3 and 6.1.0 stores user credentials in plain clear text which can be read by a local user with container access. IBM X-Force ID: 255585. | Sterling_external_authentication_server, Sterling_secure_proxy | 5.5 | ||
| 2024-03-15 | CVE-2023-46179 | IBM Sterling Secure Proxy 6.0.3 and 6.1.0 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 269683. | Sterling_secure_proxy | 4.3 | ||
| 2024-03-15 | CVE-2023-46182 | IBM Sterling Secure Proxy 6.0.3 and 6.1.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 269692. | Sterling_secure_proxy | 5.4 | ||
| 2024-03-15 | CVE-2023-47162 | IBM Sterling Secure Proxy 6.0.3 and 6.1.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 270973. | Sterling_secure_proxy | 6.1 | ||
| 2024-03-15 | CVE-2023-46181 | IBM Sterling Secure Proxy 6.0.3 and 6.1.0 allows web pages to be stored locally which can be read by another user on the system. IBM X-Force ID: 269686. | Sterling_secure_proxy | 3.3 |