CVE-2022-21826: XSS

Published Sep 30, 2022
·
Updated

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.

Affected Software

77 affected components
PulseSecure Pulse Connect Secure<9.1
PulseSecure Pulse Connect Secure=9.1
PulseSecure Pulse Connect Secure=9.1-r1
PulseSecure Pulse Connect Secure=9.1-r1.0
PulseSecure Pulse Connect Secure=9.1-r10.0
PulseSecure Pulse Connect Secure=9.1-r10.2
PulseSecure Pulse Connect Secure=9.1-r11.0
PulseSecure Pulse Connect Secure=9.1-r11.1
PulseSecure Pulse Connect Secure=9.1-r11.3
PulseSecure Pulse Connect Secure=9.1-r11.4
PulseSecure Pulse Connect Secure=9.1-r12
PulseSecure Pulse Connect Secure=9.1-r12.1
PulseSecure Pulse Connect Secure=9.1-r12.2
PulseSecure Pulse Connect Secure=9.1-r13
PulseSecure Pulse Connect Secure=9.1-r15
PulseSecure Pulse Connect Secure=9.1-r2
PulseSecure Pulse Connect Secure=9.1-r2.0
PulseSecure Pulse Connect Secure=9.1-r3
PulseSecure Pulse Connect Secure=9.1-r3.0
PulseSecure Pulse Connect Secure=9.1-r4
PulseSecure Pulse Connect Secure=9.1-r4.0
PulseSecure Pulse Connect Secure=9.1-r4.1
PulseSecure Pulse Connect Secure=9.1-r4.2
PulseSecure Pulse Connect Secure=9.1-r4.3
PulseSecure Pulse Connect Secure=9.1-r5
PulseSecure Pulse Connect Secure=9.1-r5.0
PulseSecure Pulse Connect Secure=9.1-r6
PulseSecure Pulse Connect Secure=9.1-r6.0
PulseSecure Pulse Connect Secure=9.1-r7
PulseSecure Pulse Connect Secure=9.1-r7.0
PulseSecure Pulse Connect Secure=9.1-r8
PulseSecure Pulse Connect Secure=9.1-r8.0
PulseSecure Pulse Connect Secure=9.1-r8.1
PulseSecure Pulse Connect Secure=9.1-r8.2
PulseSecure Pulse Connect Secure=9.1-r8.4
PulseSecure Pulse Connect Secure=9.1-r9
PulseSecure Pulse Connect Secure=9.1-r9.0
PulseSecure Pulse Connect Secure=9.1-r9.1
PulseSecure Pulse Connect Secure=9.1-r9.2
Ivanti Connect Secure=9.1
Ivanti Connect Secure=9.1-r1
Ivanti Connect Secure=9.1-r1.0
Ivanti Connect Secure=9.1-r10.0
Ivanti Connect Secure=9.1-r10.2
Ivanti Connect Secure=9.1-r11.0
Ivanti Connect Secure=9.1-r11.1
Ivanti Connect Secure=9.1-r11.3
Ivanti Connect Secure=9.1-r11.4
Ivanti Connect Secure=9.1-r12
Ivanti Connect Secure=9.1-r12.1
Ivanti Connect Secure=9.1-r12.2
Ivanti Connect Secure=9.1-r13
Ivanti Connect Secure=9.1-r15
Ivanti Connect Secure=9.1-r2
Ivanti Connect Secure=9.1-r2.0
Ivanti Connect Secure=9.1-r3
Ivanti Connect Secure=9.1-r3.0
Ivanti Connect Secure=9.1-r4
Ivanti Connect Secure=9.1-r4.0
Ivanti Connect Secure=9.1-r4.1
Ivanti Connect Secure=9.1-r4.2
Ivanti Connect Secure=9.1-r4.3
Ivanti Connect Secure=9.1-r5
Ivanti Connect Secure=9.1-r5.0
Ivanti Connect Secure=9.1-r6
Ivanti Connect Secure=9.1-r6.0
Ivanti Connect Secure=9.1-r7
Ivanti Connect Secure=9.1-r7.0
Ivanti Connect Secure=9.1-r8
Ivanti Connect Secure=9.1-r8.0
Ivanti Connect Secure=9.1-r8.1
Ivanti Connect Secure=9.1-r8.2
Ivanti Connect Secure=9.1-r8.4
Ivanti Connect Secure=9.1-r9
Ivanti Connect Secure=9.1-r9.0
Ivanti Connect Secure=9.1-r9.1
Ivanti Connect Secure=9.1-r9.2

Event History

Sep 30, 2022
CVE Published
via MITRE·04:24 PM
Data Sourced
via MITRE·04:24 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-21826?

CVE-2022-21826 is a vulnerability in Pulse Secure version 9.115 and below that enables client-side HTTP request smuggling.

2

How does CVE-2022-21826 affect Pulse Secure?

CVE-2022-21826 affects Pulse Secure version 9.115 and below by allowing an attacker to perform client-side HTTP request smuggling.

3

What is the severity of CVE-2022-21826?

CVE-2022-21826 has a severity rating of medium with a CVSS score of 5.4.

4

How can I fix CVE-2022-21826 in Pulse Secure?

To fix CVE-2022-21826 in Pulse Secure, you should update to a version higher than 9.115.

5

Where can I find more information about CVE-2022-21826?

You can find more information about CVE-2022-21826 at the following link: [Pulse Security Advisories](https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/Client-Side-Desync-Attack/)

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203