How to Fix CVE-2023-46217: Wavelink (Bundle Sibling)

CVE-2023-46217 is a sibling vulnerability in the same Ivanti Wavelink advisory bundle as CVE-2023-41727. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2023-46217 is the same as for the primary write-up.

What's different about CVE-2023-46217?

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.

The technical distinction is the specific code path or input vector listed in the description above. Impact is consistent with the bundle: a denial-of-service condition on the affected service. The patched build addresses every code path in the advisory in one update.

How to fix CVE-2023-46217

Apply the patched build per the primary write-up: How to Fix CVE-2023-41727.

Frequently asked questions

Is CVE-2023-46217 actively exploited?

Yes. CVE-2023-46217 is on the CISA Known Exploited Vulnerabilities catalog, so federal civilian agencies are required to patch on the published deadline. Most enterprises treat the same date as the practical floor.

What is the CVSS severity of CVE-2023-46217?

Critical. See the advisory for the full CVSS vector.

Where can I read the official advisory?

See https://download.wavelink.com/Files/avalanche_v6.4.2_release_notes.txt

Does the patch require a reboot?

It depends on the deployment. Service-only updates usually need a service restart; OS-level fixes require a full reboot. Check the vendor release notes for the exact post-upgrade steps.

References

• Official vendor advisory: https://download.wavelink.com/Files/avalanche_v6.4.2_release_notes.txt
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46217
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2023-41727

*Written by Sai Kiran Pandrala on 2026-05-25. Part of the Ivanti Wavelink bundle. Full procedure at how-to-fix-cve-2023-41727.*