dbcve.org
AvalancheApplication · Ivanti

CVE-2023-32561

HIGH · 7.5 CVSS v3.1 Published 2023-08-10
Fix available
A fix is available. Upgrade to 6.4.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 previously generated artifact by an administrator could be accessed by an attacker. The contents of this artifact could lead to authentication bypass. Fixed in version 6.4.1.

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 · moderate confidence

An authentication bypass vulnerability exists where an attacker can access a previously generated administrative artifact. The exposed artifact contains authentication-related data that can be leveraged to bypass authentication controls. This appears to be a privilege escalation/authorization flaw in how admin-generated artifacts are protected.

MitigationUpgrade to version 6.4.1. Additionally, review and rotate any admin-generated artifacts (tokens, keys, session data) created prior to the patch, as these may have been compromised.

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
AvalancheApplication
Affected:< 6.4.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installed Ivanti Avalanche version
    Check the application version through the administration console, installer properties, or product documentation. Common locations include the About section in the web UI, the installer MSI properties, or the version file in the application directory.
    Affected if The installed version is lower than 6.4.1 (for example, 6.4.0, 6.3.x, or earlier)
  2. Locate admin-generated authentication artifacts
    Search for authentication-related files such as session tokens, API keys, administrative credentials, or configuration files that store authentication data. Check common directories: config folders, data directories, and the web application root.
    Affected if Any authentication artifacts (tokens, keys, session data) exist in the environment from versions prior to 6.4.1
  3. Verify file system permissions on artifact storage
    Examine file system permissions on directories containing admin artifacts. Ensure that unauthorized users or processes cannot read authentication-related configuration or data files.
    Affected if Artifacts are stored in locations with weak or overly permissive access controls
  4. Review artifact generation and protection mechanisms
    Inspect the application configuration to determine how administrative artifacts are created, stored, and protected. Look for settings related to token generation, session management, and credential storage.
    Affected if The configuration shows artifacts are generated without proper protection or are stored in plaintext
  5. Audit existing admin sessions and tokens
    Query the system for active administrative sessions or tokens. Check if multiple or unexpected tokens exist, or if sessions from prior time periods remain valid.
    Affected if Multiple valid admin artifacts exist or sessions persist beyond expected duration

A user is affected if their Ivanti Avalanche installation is version 6.4.0 or earlier AND contains admin-generated authentication artifacts from before the patch was applied.

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 6.4.1 or later
Fixed in 6.4.1
Interim mitigation

Upgrade to version 6.4.1. Additionally, review and rotate any admin-generated artifacts (tokens, keys, session data) created prior to the patch, as these may have been compromised.

Recommended fix High confidence

6.4.1

  1. Ensure you have a complete backup of your current Avalanche configuration and database
  2. Download Avalanche version 6.4.1 or later from the official Ivanti support portal
  3. Review Ivanti's official upgrade documentation for Avalanche
  4. Execute the upgrade following the standard upgrade procedure for your deployment type
  5. After upgrade, verify that the previously generated artifacts are no longer accessible to unauthorized users
  6. Confirm the version number post-upgrade matches 6.4.1 or later

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32561 — 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-2023-32561 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