dbcve.org
Connect SecureApplication · Ivanti

CVE-2025-0283

HIGH · 7.0 CVSS v3.1 Published 2025-01-08
Fix available
A fix is available. Upgrade to 9.1 / 22.7 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability exists in Ivanti Connect Secure, Ivanti Policy Secure, and Ivanti Neurons for ZTA gateways. The flaw allows a locally authenticated attacker to overflow a stack buffer and execute arbitrary code with elevated privileges, achieving privilege escalation from authenticated user to administrator or root-level access.

MitigationApply the vendor-supplied patches: upgrade Ivanti Connect Secure to 22.7R2.5 or later, Ivanti Policy Secure to 22.7R1.2 or later, and Ivanti Neurons for ZTA gateways to 22.7R2.3 or later. Restrict local administrative access to trusted personnel as an additional defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Connect SecureApplication
Affected:< 9.1>= 22.2, < 22.7= 9.1= 21.9= 21.12= 22.1= 22.7
Neurons For Zero Trust AccessApplication
Affected:all versions= 22.2= 22.3= 22.4= 22.5= 22.6= 22.7
Policy SecureApplication
Affected:< 22.7= 22.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Ivanti product
    Determine which Ivanti product is running in your environment: Ivanti Connect Secure, Ivanti Policy Secure, or Ivanti Neurons for Zero Trust Access. Check the product name in the admin console or system information page.
    Affected if The system runs any of the three listed products.
  2. Determine the installed version of Ivanti Connect Secure
    If using Ivanti Connect Secure, access the admin dashboard and navigate to System > Upgrade/Backup > Upgrade > View Current Version, or use the command line and run 'show version' to retrieve the firmware version.
    Affected if The version is less than 9.1, equal to 9.1, 21.9, 21.12, 22.1, 22.7, or between 22.2 and 22.6 inclusive.
  3. Determine the installed version of Ivanti Policy Secure
    If using Ivanti Policy Secure, access the admin console and check System > Configuration > Upgrade/Backup > View Current Version, or run 'show version' from the CLI.
    Affected if The version is less than 22.7 or equal to 22.7.
  4. Determine the installed version of Ivanti Neurons for ZTA
    If using Ivanti Neurons for Zero Trust Access, check the gateway version through the admin portal under Gateway > Overview or by accessing system information via the management interface.
    Affected if Any version is installed, as all versions are affected per the advisory.
  5. Verify if local administrative access is enabled
    Check the authentication configuration in the admin console under Users > Local Users or Authentication > Auth Servers to determine if local user authentication is configured and enabled.
    Affected if Local authenticated user accounts exist and are permitted access, as the vulnerability requires a locally authenticated attacker to achieve privilege escalation.

A user is affected if they are running any of the three Ivanti products at the vulnerable versions listed and have local authentication enabled, allowing a locally authenticated attacker to potentially escalate to administrator or root privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.1 / 22.7 or later
Fixed in 9.122.7
Interim mitigation

Apply the vendor-supplied patches: upgrade Ivanti Connect Secure to 22.7R2.5 or later, Ivanti Policy Secure to 22.7R1.2 or later, and Ivanti Neurons for ZTA gateways to 22.7R2.3 or later. Restrict local administrative access to trusted personnel as an additional defense-in-depth measure.

Recommended fix High confidence

Ivanti Connect Secure: 22.7R2.5 | Ivanti Policy Secure: 22.7R1.2 | Ivanti Neurons for ZTA: 22.7R2.3

  1. Identify the specific Ivanti product in use (Connect Secure, Policy Secure, or Neurons for ZTA)
  2. Access the product's administrative interface or console
  3. Navigate to the system upgrade or firmware update section
  4. Download the appropriate fixed version: Connect Secure upgrade to 22.7R2.5, Policy Secure upgrade to 22.7R1.2, or Neurons for ZTA upgrade to 22.7R2.3
  5. Apply the upgrade following vendor documentation
  6. Verify the upgrade was successful and the version matches the fixed release
  7. Confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Secure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0283 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data