# CVE-2023-46805: Ivanti Connect Secure and Policy Secure Authentication Bypass

> Remote attackers can bypass authentication controls to access restricted resources in Ivanti ICS and Policy Secure web components.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Yes, since 10 Jan 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2024
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-m2pj-mjhw-x9fm

## What is CVE-2023-46805?

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

### Official description

An authentication bypass vulnerability in the web component of Ivanti ICS 9.x, 22.x and Ivanti Policy Secure allows a remote attacker to access restricted resources by bypassing control checks.

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Ivanti Connect Secure, Ivanti Policy Secure.

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

No fix has been published for CVE-2023-46805 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 22 Jan 2024.

## Is CVE-2023-46805 being exploited?

Yes. Attackers have exploited CVE-2023-46805 in the wild since at least 10 Jan 2024, including in ransomware campaigns.

Public exploit code:

- An authentication bypass vulnerability in the web component of Ivanti ICS 9.x, 22.x and Ivanti Policy Secure allows a remote attacker to access restricted resources by bypassing control checks. (github_poc): https://github.com/duy-31/CVE-2023-46805_CVE-2024-21887
- Ivanti Pulse Secure CVE-2023-46805 Scanner - Based on Assetnote's Research (github_poc): https://github.com/Chocapikk/CVE-2023-46805
- Mitigation validation utility for the Ivanti Connect Around attack chain. Runs multiple checks. CVE-2023-46805, CVE-2024-21887. (github_poc): https://github.com/seajaysec/Ivanti-Connect-Around-Scan
- Scanner for CVE-2023-46805 - Ivanti Connect Secure (github_poc): https://github.com/yoryio/CVE-2023-46805
- A Python script for examining Ivanti Secure Connect (ICS) event logs, designed to support investigations into vulnerabilities CVE-2025-0282, CVE-2023-46805, and CVE-2024-21887. (github_poc): https://github.com/Hexastrike/Ivanti-Connect-Secure-Logs-Parser
- Simple scanner for scanning a list of ip-addresses for vulnerable Ivanti Pulse Secure devices (github_poc): https://github.com/cbeek-r7/CVE-2023-46805

## 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-2023-46805 and fix it if it is affected.

What it is: CVE-2023-46805 is a high-severity authentication bypass vulnerability in Ivanti Connect Secure, published on 12 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-46805 in the wild since at least 10 Jan 2024, including in ransomware campaigns.

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-2023-46805/ (Markdown: https://insights.sbomify.com/CVE-2023-46805/index.md)
```

## Sources

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

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