# CVE-2022-36980: Race condition in Avalanche

> Remote attackers can bypass authentication in Ivanti Avalanche due to a race condition in the EnterpriseServer service.

- **Severity:** Critical 9.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** 29 Mar 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-29cx-mrrh-g7pc

## What is CVE-2022-36980?

CVE-2022-36980 is a critical vulnerability in Ivanti Avalanche, published on 29 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability allows remote attackers to bypass authentication on affected installations of Ivanti Avalanche 6.3.2.3490. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the EnterpriseServer service. The issue results from the lack of proper locking when performing operations during authentication. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-15528.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2022-36980?

It affects 1 product.


Products: Ivanti Avalanche.

## How do I fix CVE-2022-36980?

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

## Is CVE-2022-36980 being exploited?

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

## Other vulnerabilities in Ivanti Avalanche

- [CVE-2023-38036](https://insights.sbomify.com/CVE-2023-38036/): Memory corruption in Avalanche (critical 9.8)
- [CVE-2024-24996](https://insights.sbomify.com/CVE-2024-24996/): Memory corruption in Avalanche (critical 9.8)
- [CVE-2024-29204](https://insights.sbomify.com/CVE-2024-29204/): Memory corruption in Avalanche (critical 9.8)
- [CVE-2023-41727](https://insights.sbomify.com/CVE-2023-41727/): Memory corruption in Wavelink (critical 9.8)
- [CVE-2023-46216](https://insights.sbomify.com/CVE-2023-46216/): Memory corruption in Wavelink (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36980 and fix it if it is affected.

What it is: CVE-2022-36980 is a critical vulnerability in Ivanti Avalanche, published on 29 Mar 2023. 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-2022-36980 in the wild and no public exploit code.

Affected product: Ivanti Avalanche. 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-2022-36980/ (Markdown: https://insights.sbomify.com/CVE-2022-36980/index.md)
```

## Sources

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

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