Administrative service interruption via stack buffer overflow
Published Nov 12, 2024 · Updated Nov 19, 2024
Stack buffer overflow in Ivanti Connect Secure before 22.7R2.3 and Policy Secure before 22.7R1.2 allows remote authenticated users to crash the service. Ivanti identifies the memory-corruption locus only as a stack-based buffer overflow and has not published the affected request handler or the unchecked input copied into the stack buffer. Exploitation requires remote access and an authenticated administrator account; the documented consequence is a service crash, with no confidentiality or integrity impact.
Summary
What happened
Stack buffer overflow in Ivanti Connect Secure before 22.7R2.3 and Policy Secure before 22.7R1.2 allows remote authenticated users to crash the service. Ivanti identifies the memory-corruption locus only as a stack-based buffer overflow and has not published the affected request handler or the unchecked input copied into the stack buffer. Exploitation requires remote access and an authenticated administrator account; the documented consequence is a service crash, with no confidentiality or integrity impact.
The record
- CVE
- CVE-2024-47909
- Published
- Nov 12, 2024
- Updated
- Nov 19, 2024
- Vendor
- Ivanti
- Product
- Connect Secure
- Classifications
- CWE-787, CWE-121, T1499
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 19, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
Weakness, pattern, technique
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