# CVE-2019-11213: Auth bypass in n/a

> Attackers with local access can steal session tokens to hijack user sessions and gain unauthorized access to Pulse Secure clients.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q822-4vp5-26qj

## What is CVE-2019-11213?

CVE-2019-11213 is a high-severity authentication bypass vulnerability in Ivanti Connect Secure, published on 12 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Pulse Secure Pulse Desktop Client and Network Connect, an attacker could access session tokens to replay and spoof sessions, and as a result, gain unauthorized access as an end user, a related issue to CVE-2019-1573. (The endpoint would need to be already compromised for exploitation to succeed.) This affects Pulse Desktop Client 5.x before Secure Desktop 5.3R7 and Pulse Desktop Client 9.x before Secure Desktop 9.0R3. It also affects (for Network Connect customers) Pulse Connect Secure 8.1 before 8.1R14, 8.3 before 8.3R7, and 9.0 before 9.0R3.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2019-11213?

It affects 3 products.


Products: Ivanti Connect Secure, Pulsesecure Pulse Connect Secure, Pulsesecure Pulse Secure Desktop Client.

## How do I fix CVE-2019-11213?

No fix has been published for CVE-2019-11213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-11213 being exploited?

There is no known exploitation of CVE-2019-11213 in the wild and no public exploit code.

## Other vulnerabilities in Ivanti Connect Secure

- [CVE-2021-22893](https://insights.sbomify.com/CVE-2021-22893/): Ivanti Pulse Connect Secure Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2019-11510](https://insights.sbomify.com/CVE-2019-11510/): Ivanti Pulse Connect Secure Arbitrary File Read (critical 9.9, exploited in the wild)
- [CVE-2024-21887](https://insights.sbomify.com/CVE-2024-21887/): Ivanti Connect Secure and Policy Secure Command Injection (critical 9.1, exploited in the wild)
- [CVE-2025-22457](https://insights.sbomify.com/CVE-2025-22457/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)
- [CVE-2025-0282](https://insights.sbomify.com/CVE-2025-0282/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11213 and fix it if it is affected.

What it is: CVE-2019-11213 is a high-severity authentication bypass vulnerability in Ivanti Connect Secure, published on 12 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11213 in the wild and no public exploit code.

Affected product: Ivanti Connect Secure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11213/ (Markdown: https://insights.sbomify.com/CVE-2019-11213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11213
- OSV: https://osv.dev/vulnerability/CVE-2019-11213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11213/
Summaries are generated and may contain mistakes; the official description above is the record.