dbcve.org
AvalancheApplication · Ivanti

CVE-2023-46223

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

Memory corruption vulnerability in Mobile Device Server allows remote attackers to send specially crafted data packets causing buffer overflow or similar memory corruption, leading to potential Denial of Service or arbitrary code execution. The attack is network-exploitable and rated critical due to the high impact and likely low attack complexity.

MitigationApply vendor-provided patches for the Mobile Device Server product immediately; if no patch available, implement network segmentation and restrict access to the server from untrusted networks as a compensating control.

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. Identify if Ivanti Avalanche is installed
    Check the system for Ivanti Avalanche installation directories (typically C:\Program Files\Avalanche or C:\Program Files (x86)\Avalanche) or look in Windows Programs and Features for 'Ivanti Avalanche' entry
    Affected if Ivanti Avalanche software is present on the system
  2. Determine installed Ivanti Avalanche version
    Locate the Avalanche installation and check the version information - commonly found in the application's About dialog, in the installation directory as a version file, or in Windows Registry under HKLM\SOFTWARE\LANDesk\ManagementSuite or similar Avalanche registry keys
    Affected if The installed version is lower than 6.4.2 (e.g., 6.4.1, 6.4.0, 6.3.x, etc.)
  3. Verify Mobile Device Server component status
    Check if the Mobile Device Server (MDS) service is running - look for 'Avalanche Mobile Device Server' or 'MDServer' in Windows Services, or check the Avalanche administration console for MDS component status
    Affected if Mobile Device Server service is installed and running
  4. Check network exposure of Mobile Device Server
    Identify which network ports the Mobile Device Server is listening on (common ports include 8080, 8443, or custom ports configured during installation) using 'netstat -ano' command or by reviewing the server configuration in Avalanche console
    Affected if MDS is exposed to untrusted networks (listening on 0.0.0.0 or accessible via external IP without firewall restrictions)
  5. Review firewall and access control rules
    Examine Windows Firewall rules and any network filtering devices for rules allowing inbound traffic to Avalanche/MDS ports from untrusted network segments
    Affected if Firewall rules permit unrestricted inbound access to MDS ports from outside the trusted network

A system is affected if Ivanti Avalanche with Mobile Device Server is installed and running a version lower than 6.4.2, especially if the MDS component is network-accessible from untrusted networks.

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-provided patches for the Mobile Device Server product immediately; if no patch available, implement network segmentation and restrict access to the server from untrusted networks as a compensating control.

Recommended fix High confidence

Avalanche 6.4.2 or later

  1. 1. Navigate to the official Wavelink download portal at download.wavelink.com
  2. 2. Locate and download Avalanche version 6.4.2 or later
  3. 3. Back up the current Avalanche configuration and database before upgrading
  4. 4. Stop the Avalanche Mobile Device Server service
  5. 5. Install the upgraded Avalanche 6.4.2 package
  6. 6. Start the Avalanche Mobile Device Server service
  7. 7. Verify the server is running and accessible
  8. 8. Test that Mobile Device Management functionality is operating normally
Caveat Review the release notes for version 6.4.2 to confirm no breaking changes affect your deployment; security patches typically maintain backward compatibility

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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