dbcve.org
AvalancheApplication · Ivanti

CVE-2023-46264

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-19
Fix available
A fix is available. Upgrade to 6.4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
An unrestricted upload of file with dangerous type vulnerability exists in Avalanche versions 6.4.1 and below that could allow an attacker to achieve a remove code execution.

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 unrestricted file upload vulnerability in Avalanche versions 6.4.1 and below allows attackers to upload files with dangerous types (e.g., executable scripts) to the server, enabling remote code execution. The application lacks proper validation of file extensions, MIME types, and file content before saving uploaded files.

MitigationUpgrade to Avalanche version 6.4.2 or later. Implement strict allowlist-based file type validation including both extension checking and magic-byte/content analysis, store uploads outside webroot, and disable script execution in upload directories.

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.2

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. Determine installed Avalanche version
    Locate the Avalanche installation directory and check the version file or executable properties. Common locations include C:\Program Files\Avalanche or /opt/avalanche. Look for a version.txt, about dialog, or check the installer/-service version metadata.
    Affected if Installed version is 6.4.1 or lower (less than 6.4.2)
  2. Identify Avalanche web interface accessibility
    Determine if the Avalanche web console is exposed by checking the service status and listening ports. Use 'netstat -an | findstr 8080' or similar to see if the Avalanche web server port is open and accessible.
    Affected if The Avalanche web interface port (typically 8080 or 8443) is open and reachable from a network where untrusted users could access it
  3. Verify file upload endpoint exposure
    Check if the /upload or similar file upload API endpoint exists and is accessible on the Avalanche web server. This may require reviewing the web application's exposed URLs or proxy configuration.
    Affected if The file upload functionality is exposed via the web interface without additional authentication barriers
  4. Review upload directory configuration
    Inspect the Avalanche configuration files or web server settings to determine where uploaded files are stored and whether the directory is within the web root.
    Affected if Uploaded files are stored in a location accessible via the web server (within webroot) and script execution is not disabled for that directory
  5. Check for existing suspicious uploaded files
    Search the configured upload directories for file extensions that indicate executable content (.jsp, .asp, .php, .exe, .sh, .bat, .cmd). Use file system search tools to enumerate files with these extensions.
    Affected if Any executable script files or potentially malicious content exists in upload directories

You are affected if your installed Ivanti Avalanche version is below 6.4.2 and the file upload web interface is accessible to untrusted users.

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.2 or later
Fixed in 6.4.2
Interim mitigation

Upgrade to Avalanche version 6.4.2 or later. Implement strict allowlist-based file type validation including both extension checking and magic-byte/content analysis, store uploads outside webroot, and disable script execution in upload directories.

Recommended fix Moderate confidence

Avalanche 6.4.2

  1. 1. Back up your current Avalanche installation and configuration before proceeding with any updates.
  2. 2. Download Avalanche version 6.4.2 or later from the official vendor source (download.wavelink.com or vendor's support portal).
  3. 3. Verify the integrity of the downloaded package using checksums if provided by the vendor.
  4. 4. Stop the Avalanche service to ensure a clean update process.
  5. 5. Install the updated Avalanche version 6.4.2 or higher following the vendor's documented upgrade procedure.
  6. 6. After installation, verify that the service starts successfully and the web interface is accessible.
  7. 7. Confirm the new version is installed by checking the Avalanche about or version information.
  8. 8. Test that file upload functionality works correctly with legitimate file types to verify the fix is functioning properly.

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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