CVE-2022-21826
This body ends up prefixing the next HTTP request sent down that connection, this means when someone loads website attacker may be able to make browser issue a POST to the application, enabling XSS.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 45.2%, higher than 99% of all known CVEs. Patch or mitigate before the next change window.
Description
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 that connection, this means when someone loads website attacker may be able to make browser issue a POST to the application, enabling XSS.
- CVSS 3.1
- 5.4 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- EPSS
- 45.23% probability · 99th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-444
- Affected
- ivanti/connect secure · pulsesecure/pulse connect secure
- Source
- support@hackerone.com
References
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.