# CVE-2023-41726: Privilege escalation in Avalanche

> Local attackers can escalate privileges due to incorrect default permissions in Ivanti Avalanche.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2023
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-7gmv-4hrv-rx2g

## What is CVE-2023-41726?

CVE-2023-41726 is a high-severity vulnerability in Ivanti Avalanche, published on 3 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Ivanti Avalanche Incorrect Default Permissions allows Local Privilege Escalation Vulnerability

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2023-41726?

It affects 1 product.


Products: Ivanti Avalanche.

## How do I fix CVE-2023-41726?

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

## Is CVE-2023-41726 being exploited?

There is no known exploitation of CVE-2023-41726 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-2023-41726 and fix it if it is affected.

What it is: CVE-2023-41726 is a high-severity vulnerability in Ivanti Avalanche, published on 3 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41726 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-2023-41726/ (Markdown: https://insights.sbomify.com/CVE-2023-41726/index.md)
```

## Sources

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

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