dbcve.org
Connect SecureApplication · Ivanti

CVE-2022-21826

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-30
Fix available
A fix is available. Upgrade to 9.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Pulse Secure versions 9.115 and below contain a client-side HTTP request smuggling vulnerability. When processing POST requests, the application ignores the Content-Length header and leaves the POST body data on the TCP/TLS socket. This residual body then prefixes the next HTTP request sent over that connection, allowing attackers to inject malicious content and potentially achieve XSS via browser-based attacks.

MitigationUpgrade Pulse Secure to a version above 9.115; alternatively, implement WAF rules or HTTP desync mitigation controls to detect and block malformed Content-Length requests, and ensure proper connection handling configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Connect SecureApplication
Affected:= 9.1
Pulse Connect SecureApplication
Affected:< 9.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed product name
    Access the admin interface or CLI and confirm the product is either Pulse Connect Secure or Ivanti Connect Secure. In the admin dashboard, check the system information or use the CLI command 'show system information' or 'get system version' to display the product name.
    Affected if The product is Pulse Connect Secure or Ivanti Connect Secure
  2. Determine the installed version number
    In the admin interface, navigate to System > Status or use the CLI command 'show version' to display the exact firmware/software version number.
    Affected if The displayed version is 9.115 or lower for Pulse Connect Secure, or exactly 9.1 for Ivanti Connect Secure
  3. Confirm the web service is running
    Check if the HTTPS admin interface or web portal is accessible by attempting to reach the device's IP or hostname over ports 443 or 8443. Use a network scanner or verify the service status via CLI with 'show web-server status' if available.
    Affected if The web service is running and accepting HTTP/HTTPS connections on the affected product versions
  4. Check for active HTTP processing
    Review the device configuration to confirm HTTP or HTTPS processing is enabled for the admin interface or user portal. In the CLI, use 'show web' or 'show http-server configuration' to inspect enabled protocols.
    Affected if HTTP/HTTPS processing is enabled on the vulnerable version

You are affected if the product is Pulse Connect Secure version 9.115 or lower, or Ivanti Connect Secure version 9.1, and the web interface is actively processing HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.1 or later
Fixed in 9.1
Interim mitigation

Upgrade Pulse Secure to a version above 9.115; alternatively, implement WAF rules or HTTP desync mitigation controls to detect and block malformed Content-Length requests, and ensure proper connection handling configurations.

Recommended fix Moderate confidence

Latest Pulse Connect Secure 9.x release (version > 9.115)

  1. Check current Pulse Connect Secure version in admin console under System > Status
  2. Download the latest Pulse Connect Secure software from kb.pulsesecure.net or the official support portal
  3. Review upgrade instructions in the Pulse Connect Secure Admin Guide
  4. Schedule a maintenance window and backup current configuration
  5. Deploy the upgrade in a staging environment first if possible
  6. Apply the upgrade to production following standard Pulse Secure upgrade procedures
  7. Verify the upgrade was successful and the vulnerability is resolved
Caveat Standard upgrade risks apply - test in non-production first; review release notes for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Secure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21826 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21826 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data