CVE-2025-8310
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 · uneditedMissing authorization in the admin console of Ivanti Virtual Application Delivery Controller before version 22.9 allows a remote authenticated attacker to take over admin accounts by resetting the password
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 confidenceMissing authorization check in the admin console of Ivanti Virtual Application Delivery Controller versions before 22.9 allows any authenticated remote attacker to reset arbitrary admin account passwords, enabling complete admin account takeover and potential infrastructure compromise.
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< 22.9CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ivanti Virtual Application Delivery Controller installationLocate the installation directory or check running services for 'Ivanti' or 'Virtual Application Delivery Controller' processes on the systemAffected if The product is installed and running on the system
-
Determine installed versionCheck the product's version information through its admin console, installation directory, or version command specific to the applianceAffected if The installed version cannot be determined or is displayed
-
Compare version against vulnerability rangeReview the version number against the affected range: any version before 22.9 (such as 22.8, 22.7, earlier releases) is vulnerableAffected if The installed version is lower than 22.9 (for example, 22.8.x or earlier)
-
Verify admin console accessibilityConfirm the admin console web interface is accessible and authentication mechanisms are in placeAffected if The admin console is reachable and accepts authentication
Your environment is affected if Ivanti Virtual Application Delivery Controller is installed and the running version is any release earlier than 22.9.
Generated from the published advisory. Verify against your own configuration.
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 · scoped22.9
Upgrade Ivanti Virtual Application Delivery Controller to version 22.9 or later to apply the vendor patch addressing the missing authorization vulnerability.
22.9
- Ensure you have a complete backup of the current Virtual Application Delivery Controller configuration
- Schedule a maintenance window for the upgrade procedure
- Download the Virtual Application Delivery Controller version 22.9 from the official Ivanti support portal
- Follow the standard upgrade procedure documented in the Ivanti Virtual Application Delivery Controller administration guide
- After upgrading, verify the admin console is accessible and all services are running
- Confirm the version number displays 22.9 or later in the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8310 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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