548 matches found
SA44440 - April 21 2020 OpenSSL Security Advisory
Last Modified Date Aug 24, 2026 12:35:11 AM...
SA40202 - [Pulse Secure] May 3rd 2016 OpenSSL Security Advisory
Last Modified Date Mar 4, 2024 7:46:08 PM...
SA44574 - 2020-08: Out-of-Cycle Advisory: FBI and NSA Expose New Linux Malware Drovorub
Last Modified Date Mar 4, 2024 6:00:01 PM...
SA44790 - HTTP Request Smuggling vulnerability with Virtual Traffic Manager (vTM)
Last Modified Date Mar 4, 2024 8:03:28 PM...
SA44508 - 2020-06: Out-of-Cycle Advisory: Multiple Vulnerabilities in Treck TCP/IP Embedded Software
Last Modified Date Mar 4, 2024 5:58:50 PM...
SA44845 - OpenSSL Security Advisory CVE-2021-3450
Last Modified Date Aug 24, 2026 1:12:25 AM...
SA44676 - December 08 2020 OpenSSL Security Advisory
Last Modified Date Dec 15, 2023 5:32:46 PM...
SA44601 - 2020-10: Security Bulletin: Multiple Vulnerabilities Resolved in Pulse Connect Secure / Pulse Policy Secure / Pulse Secure Desktop Client 9.1R9
Edit: 4th of March 2024 - This isn't an active SA and any new edits are part of an article maintenance project. This advisory provides information about multiple vulnerabilities resolved in Pulse Connect Secure 9.1R9, Pulse Policy Secure 9.1R9 and Pulse Secure Desktop Client 9.1R9. Refer to KB438...
SA45100 - CVE-2022-0778-OpenSSL-Vulnerability may lead to DoS attack
Last Modified Date Dec 15, 2023 5:27:41 PM...
SA44846 - OpenSSL Security Advisory CVE-2021-23841
Last Modified Date Aug 23, 2026 11:06:07 PM...
SA44712 - 2021-02: Out-of-Cycle Advisory: Pulse Secure response to BIOS Trickboot Vulnerability
Last Modified Date Aug 24, 2026 12:35:09 AM...
SA44899 - CVE-2021-22965: A Vulnerability in Pulse Connect Secure Before 9.1R12.1
Last Modified Date Aug 24, 2026 1:12:26 AM...
Hackers Actively Exploiting Citrix ADC and Gateway Zero-Day Vulnerability
The U.S. National Security Agency NSA on Tuesday said a threat actor tracked as APT5 has been actively exploiting a zero-day flaw in Citrix Application Delivery Controller ADC and Gateway to take over affected systems. The critical remote code execution vulnerability, identified as CVE-2022-27518...
Pulse Secure Pulse Connect Secure 安全漏洞
Pulse Secure Pulse Connect Secure aka PCS, formerly known as Juniper Junos Pulse is an SSL VPN solution from Pulse Secure, Inc. in the United States. A security vulnerability exists in Pulse Secure Pulse Connect Secure. No information about this vulnerability is available at this time, so please...
CVE-2022-21826
Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down...
CVE-2022-21826
Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down...
CVE-2022-21826
Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down...
Design/Logic Flaw
Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down...
CVE-2022-21826
Pulse Connect Secure (Pulse Secure) versions 9.115 and below are affected by a client-side HTTP request smuggling vulnerability. When handling a POST request, the application may ignore the Content-Length header and keep the POST body on the TCP/TLS socket, causing the body to prefix the next HTT...
CVE-2022-21826
Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down...