CVE-2025-0283: Ivanti Connect Secure vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
A stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.5, Ivanti Policy Secure before version 22.7R1.2, and Ivanti Neurons for ZTA gateways before version 22.7R2.3 allows a local authenticated attacker to escalate their privileges.
Description quoted from the CVE record (assigned by ivanti, published 2025-01-08).
Weakness: CWE-121: Stack-based Buffer Overflow
How it can be exploited
Exploitable with local access with high attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Also known as: BDU:2025-00224, CNNVD-202501-1031, EUVD-2025-1581, GHSA-j5g5-c424-7xqg
Exploit Observer has no public exploit code that names this CVE or one of its aliases.
Research and write-ups (1)
- Research or write-up: https://unit42.paloaltonetworks.com/threat-brief-ivanti-cve-2025-0282-cve-2025-0283
Vulnerability databases and vendor advisories (8)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://access.redhat.com/security/cve/cve-2025-0283
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2025-1581
- Vulnerability database or vendor advisory: https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283
- Vulnerability database or vendor advisory: https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283?language=en_US
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-j5g5-c424-7xqg
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-0283
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202501-1031
- Vulnerability database or vendor advisory: https://www.tenable.com/cve/CVE-2025-0283
121 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.175
likely to be attacked soon - VEDAS
- 0.722
some exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Ivanti Connect Secure | Not stated | 22.7R2.5 is not affected |
| Ivanti Policy Secure | version 22.7R1.2 | Not stated |
| Ivanti Neurons for ZTA gateways | Not stated | 22.7R2.5 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: ivanti connect_secure, ivanti ivanti_neurons_for_zero_trust_access_(nzta), ivanti neurons_for_zero-trust_access, ivanti policy_secure.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.
Advisories on this CVE
- Ivanti Connect Secure zero-day (CVE-2025-0282) (8 Jan 2025)
References
Other references
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.