dbcve.org
AvalancheApplication · Ivanti

CVE-2023-32567

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-10
Fix available
A fix is available. Upgrade to 6.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Ivanti Avalanche decodeToMap XML External Entity Processing. Fixed in version 6.4.1.236

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

This is an XML External Entity (XXE) injection vulnerability in Ivanti Avalanche's decodeToMap function. The vulnerability allows remote attackers to exploit insecure XML parsing by injecting malicious external entity references, potentially enabling file disclosure, SSRF attacks, or denial of service.

MitigationApply vendor patch by upgrading Ivanti Avalanche to version 6.4.1.236 or later. If immediate patching is not feasible, disable XML external entity processing in the XML parser configuration and restrict network access to the affected service.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Ivanti Avalanche is installed
    Check for Ivanti Avalanche installation directory or running service. Common paths include C:\Program Files\Ivanti\Avalanche or /opt/avalanche. On Windows, check Services for 'Avalanche' service.
    Affected if Ivanti Avalanche software is present on the system
  2. Identify installed version
    Check the Avalanche version. Typically found in the software UI under Help > About, or check version files in the installation directory. Look for a version file or check the application banner.
    Affected if Version is displayed as less than 6.4.1 or specifically less than 6.4.1.236
  3. Verify decodeToMap function exposure
    This function processes XML input. Check if any web endpoints, API paths, or client applications send XML data to the Avalanche server. Review application logs for decodeToMap invocations if logging is enabled.
    Affected if The decodeToMap function processes XML requests from users or integrated systems
  4. Test for XXE vulnerability
    If you have access to send XML requests to Avalanche, send a test request with an external entity reference (e.g., <!ENTITY xxe SYSTEM "file:///etc/passwd">). Monitor for successful file disclosure or network access.
    Affected if The server resolves external entity references in XML input, indicating XXE is exploitable

The environment is affected if Ivanti Avalanche version is below 6.4.1.236 AND the decodeToMap function processes untrusted XML input with external entity support enabled in the parser.

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

Apply vendor patch by upgrading Ivanti Avalanche to version 6.4.1.236 or later. If immediate patching is not feasible, disable XML external entity processing in the XML parser configuration and restrict network access to the affected service.

Recommended fix High confidence

Ivanti Avalanche 6.4.1.236

  1. 1. Back up the current Ivanti Avalanche installation and database
  2. 2. Download Ivanti Avalanche version 6.4.1.236 from the official source (download.wavelink.com or Ivanti support portal)
  3. 3. Stop the Avalanche server services
  4. 4. Install version 6.4.1.236 following the standard upgrade procedure
  5. 5. Verify the installation completed successfully
  6. 6. Start the Avalanche server services
  7. 7. Validate that the decodeToMap function works correctly and the XXE vulnerability is resolved
  8. 8. Review system functionality to ensure all Avalanche features operate normally
Caveat Review Ivanti release notes for any compatibility changes or deprecated features between your current version and 6.4.1.236

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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