dbcve.org
AvalancheApplication · Ivanti

CVE-2023-46225

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
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 attacker sending specially crafted data packets to the Mobile Device Server can cause memory corruption which could result to a Denial of Service (DoS) or 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

A memory corruption vulnerability in Mobile Device Server allows remote attackers to achieve denial of service or potentially execute arbitrary code by sending specially crafted data packets. The vulnerability is network-exploitable with no authentication required, as indicated by the critical CVSS score.

MitigationApply vendor-supplied patches or updates to the Mobile Device Server software as soon as they become available. If no patch exists, consider network segmentation and restricting external access to the Mobile Device Server until a fix can be deployed.

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. Verify Ivanti Avalanche is installed
    Check the installed software inventory or application list for Ivanti Avalanche. On Windows, this can be done via Control Panel > Programs and Features, or by searching for Avalanche-related services in Services.msc.
    Affected if Ivanti Avalanche software is present on the system
  2. Determine the installed Avalanche version
    Locate the Avalanche version information. This is typically available in the application itself under Help > About, or via the Windows installer information in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or by querying the Mobile Device Server service if available.
    Affected if The installed version is lower than 6.4.2
  3. Confirm Mobile Device Server component is active
    Check if the Mobile Device Server service or process is running. On Windows, use Services.msc to look for a service related to Mobile Device Server, or use Task Manager to identify Avalanche-related processes.
    Affected if The Mobile Device Server service is running or the Mobile Device Server module is enabled in Avalanche
  4. Assess network exposure
    Review firewall rules and network configuration to determine if the Mobile Device Server port is accessible from untrusted networks. The service typically listens on configurable ports for device management connections.
    Affected if The Mobile Device Server is directly accessible from external networks or untrusted VLANs without authentication

You are affected if Ivanti Avalanche with Mobile Device Server is installed and the version is below 6.4.2, especially if the service is network-accessible.

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

Apply vendor-supplied patches or updates to the Mobile Device Server software as soon as they become available. If no patch exists, consider network segmentation and restricting external access to the Mobile Device Server until a fix can be deployed.

Recommended fix High confidence

Avalanche 6.4.2 or later

  1. 1. Obtain Avalanche version 6.4.2 or later from the official Wavelink download portal (download.wavelink.com)
  2. 2. Back up the current Avalanche configuration and database according to backup procedures
  3. 3. Stop the Avalanche Mobile Device Server service before upgrading
  4. 4. Install Avalanche version 6.4.2 using the vendor's upgrade documentation
  5. 5. Verify the Mobile Device Server starts successfully after the upgrade
  6. 6. Test that normal Mobile Device Server operations function correctly
  7. 7. Confirm the vulnerability is addressed by ensuring the service accepts only legitimate data packets
Caveat Review Wavelink release notes for any configuration or behavioral changes between your current version and 6.4.2

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

Fix this in Avalanche Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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