# CVE-2024-3652: IKEv1 default AH/ESP responder can cause libreswan to abort and restart > A remote attacker can cause a denial of service by triggering an assertion failure in Libreswan's IKEv1 responder when AES-GMAC is requested without an explicit esp configuration. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Apr 2024 - **Updated:** 27 Feb 2026 - **Also known as:** ALSA-2024:4050, ALSA-2024:4376, AZL-39919, AZL-39927, CLSA-2025-1752749664, DEBIAN-CVE-2024-3652, GHSA-395v-96gv-76w3, MGASA-2024-0138, OESA-2024-1565, RHSA-2024:4050, RHSA-2024:4200, RHSA-2024:4376, RHSA-2024:4377, RHSA-2024:4417, RHSA-2024:4431, RLSA-2024:4050, RLSA-2024:4376, UBUNTU-CVE-2024-3652 ## What is CVE-2024-3652? CVE-2024-3652 is a medium-severity denial of service vulnerability in The Libreswan Project (www.libreswan.org) libreswan, published on 11 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan's default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected. Weakness: CWE-404 (Improper Resource Shutdown or Release) ## Which versions are affected by CVE-2024-3652? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libreswan` | AlmaLinux:8 | All versions | 4.12-2.el8_10.4 | | `libreswan` | AlmaLinux:9 | All versions | 4.12-2.el9_4.1 | | `libreswan` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.12-2.el8_10.4 | | `libreswan-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.12-2.el8_10.4 | | `libreswan-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.12-2.el8_10.4 | | `libreswan` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12-2.el9_4.1 | | `libreswan-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12-2.el9_4.1 | | `libreswan-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12-2.el9_4.1 | | `libreswan` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:4.6-3.el9_0.2 | | `libreswan-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:4.6-3.el9_0.2 | | `libreswan-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:4.6-3.el9_0.2 | | `libreswan` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:4.9-3.el8_8.2 | | `libreswan-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:4.9-3.el8_8.2 | | `libreswan-debugsource` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:4.9-3.el8_8.2 | | `libreswan` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:4.9-5.el9_2.2 | | `libreswan-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:4.9-5.el9_2.2 | | `libreswan-debugsource` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:4.9-5.el9_2.2 | | `libreswan` | Red Hat:rhel_tus:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan-debuginfo` | Red Hat:rhel_tus:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan-debugsource` | Red Hat:rhel_tus:8.6::appstream | All versions | 0:4.5-1.el8_6.3 | | `libreswan` | Rocky Linux:8 | All versions | 0:4.12-2.el8_10.4 | | `libreswan` | Rocky Linux:9 | All versions | 0:4.12-2.el9_4.1 | Products: Libreswan Libreswan. ## How do I fix CVE-2024-3652? Apply the vendor's patch. ## Is CVE-2024-3652 being exploited? There is no known exploitation of CVE-2024-3652 in the wild and no public exploit code. ## Other vulnerabilities in The Libreswan Project (www.libreswan.org) libreswan - [CVE-2013-7283](https://insights.sbomify.com/CVE-2013-7283/): Race condition in n/a (critical 9.3) - [CVE-2026-12413](https://insights.sbomify.com/CVE-2026-12413/): IKEv2 Denial of Service via malformed fragmentation (high 7.5) - [CVE-2026-50721](https://insights.sbomify.com/CVE-2026-50721/): IKEv1 Denial of Service via RSA-SHA1 (PKCS#1 Version 1.5 Encrypted) authentication payload (high 7.5) - [CVE-2026-50722](https://insights.sbomify.com/CVE-2026-50722/): IKEv2 Denial of Service via RSA-SHA1 (PKCS#1 RSASSA-PKCS1-v1_5) authentication payload (high 7.5) - [CVE-2023-30570](https://insights.sbomify.com/CVE-2023-30570/): Denial of service in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3652 and fix it if it is affected. What it is: CVE-2024-3652 is a medium-severity denial of service vulnerability in The Libreswan Project (www.libreswan.org) libreswan, published on 11 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-3652 in the wild and no public exploit code. Affected product: The Libreswan Project (www.libreswan.org) libreswan. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-3652/ (Markdown: https://insights.sbomify.com/CVE-2024-3652/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3652 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3652 - OSV: https://osv.dev/vulnerability/CVE-2024-3652 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3652/ Summaries are generated and may contain mistakes; the official description above is the record.