Service crash via IPSec null pointer dereference
Published Apr 4, 2024 · Updated Oct 3, 2024
Null pointer dereference in the IPSec component of Ivanti Connect Secure 9.x and 22.x and Policy Secure allows remote attackers to crash the service. Ivanti has not published the affected function, request field, or invalid state that causes the IPSec component to dereference a null pointer. No authentication or user interaction is required, and a crafted network request interrupts the IPSec service without reported confidentiality or integrity impact.
Summary
What happened
Null pointer dereference in the IPSec component of Ivanti Connect Secure 9.x and 22.x and Policy Secure allows remote attackers to crash the service. Ivanti has not published the affected function, request field, or invalid state that causes the IPSec component to dereference a null pointer. No authentication or user interaction is required, and a crafted network request interrupts the IPSec service without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2024-22052
- Published
- Apr 4, 2024
- Updated
- Oct 3, 2024
- Vendor
- Ivanti
- Product
- Connect Secure
- Classifications
- CWE-476, CWE-703, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Oct 3, 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=22.1R6.2
- Affected versionversion=22.1R6.2 <22.1R6.2
- Affected versionversion=22.2R3
- Affected versionversion=22.2R4.2
- Affected versionversion=22.2R4.2 <22.2R4.2
- Affected versionversion=22.3R1.2
- Affected versionversion=22.3R1.2 <22.3R1.2
- Affected versionversion=22.4R1.2
- Affected versionversion=22.4R1.2 <22.4R1.2
- Affected versionversion=22.4R2.4
- Affected versionversion=22.4R2.4 <22.4R2.4
- Affected versionversion=22.5R1.3
- Affected versionversion=22.5R1.3 <22.5R1.3
- Affected versionversion=22.5R2.4
- Affected versionversion=22.5R2.4 <22.5R2.4
- Affected versionversion=22.6R1.2
- Affected versionversion=22.6R2.3
- Affected versionversion=22.6R2.3 <22.6R2.3
- Affected versionversion=9.1R14.6
- Affected versionversion=9.1R14.6 <9.1R14.6
- Affected versionversion=9.1R15.4
- Affected versionversion=9.1R15.4 <9.1R15.4
- Affected versionversion=9.1R16.4 <9.1R16.4
- Affected versionversion=9.1R17.4
- Affected versionversion=9.1R17.4 <9.1R17.4
- Affected versionversion=9.1R18.5
- Affected versionversion=9.1R18.5 <9.1R18.5
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