Unauthenticated code execution via stack buffer overflow
Published Dec 19, 2023 · Updated Aug 2, 2024
Stack-based buffer overflow in Ivanti Avalanche before 6.4.2 allows remote attackers to execute code or interrupt the service. WLAvalancheService copies attacker-controlled packet data into a fixed-size stack buffer without first validating its length. No authentication or user interaction is required, and successful exploitation runs code as SYSTEM; malformed packets can instead corrupt memory and stop the Mobile Device Server.
Summary
What happened
Stack-based buffer overflow in Ivanti Avalanche before 6.4.2 allows remote attackers to execute code or interrupt the service. WLAvalancheService copies attacker-controlled packet data into a fixed-size stack buffer without first validating its length. No authentication or user interaction is required, and successful exploitation runs code as SYSTEM; malformed packets can instead corrupt memory and stop the Mobile Device Server.
The record
- CVE
- CVE-2023-46259
- Published
- Dec 19, 2023
- Updated
- Aug 2, 2024
- Vendor
- Ivanti
- Product
- Avalanche
- Classifications
- CWE-787, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.4.1 <=6.4.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo