# CVE-2023-30570: Denial of service in n/a > Unauthenticated attackers can crash the Libreswan pluto daemon via IKEv1 Aggressive Mode packets, causing a denial of service. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 May 2023 - **Updated:** 14 Jan 2025 - **Also known as:** ALSA-2023:2122, AZL-26873, AZL-34934, DEBIAN-CVE-2023-30570, GHSA-4h3c-85v5-c6x6, OESA-2023-1318, RHSA-2023:2120, RHSA-2023:2121, RHSA-2023:2122, RHSA-2023:2123, RHSA-2023:2124, RHSA-2023:2125, RHSA-2023:2126, UBUNTU-CVE-2023-30570 ## What is CVE-2023-30570? CVE-2023-30570 is a high-severity denial of service vulnerability in n/a, published on 28 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description pluto in Libreswan before 4.11 allows a denial of service (responder SPI mishandling and daemon crash) via unauthenticated IKEv1 Aggressive Mode packets. The earliest affected version is 3.28. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2023-30570? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libreswan` | AlmaLinux:8 | All versions | 4.5-1.el8_7.1 | | `libreswan` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.5-1.el8_7.1 | | `libreswan-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.5-1.el8_7.1 | | `libreswan-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.5-1.el8_7.1 | | `libreswan` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.6-3.el9_1.1 | | `libreswan-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.6-3.el9_1.1 | | `libreswan-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.6-3.el9_1.1 | | `libreswan` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:3.29-7.el8_1.2 | | `libreswan-debuginfo` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:3.29-7.el8_1.2 | | `libreswan-debugsource` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:3.29-7.el8_1.2 | | `libreswan` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan-debuginfo` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan-debugsource` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:4.3-6.el8_4.1 | | `libreswan-debuginfo` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:4.3-6.el8_4.1 | | `libreswan-debugsource` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:4.3-6.el8_4.1 | | `libreswan` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:4.5-1.el8_6.1 | | `libreswan-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:4.5-1.el8_6.1 | | `libreswan-debugsource` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:4.5-1.el8_6.1 | | `libreswan` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:4.6-3.el9_0.1 | | `libreswan-debuginfo` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:4.6-3.el9_0.1 | | `libreswan-debugsource` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:4.6-3.el9_0.1 | | `libreswan` | Red Hat:rhel_tus:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan-debuginfo` | Red Hat:rhel_tus:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | | `libreswan-debugsource` | Red Hat:rhel_tus:8.2::appstream | All versions | 0:3.29-7.el8_2.2 | Products: Libreswan Libreswan. ## How do I fix CVE-2023-30570? Upgrade to a fixed version. ## Is CVE-2023-30570 being exploited? There is no known exploitation of CVE-2023-30570 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [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-2295](https://insights.sbomify.com/CVE-2023-2295/): Denial of service in libreswan (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-30570 and fix it if it is affected. What it is: CVE-2023-30570 is a high-severity denial of service vulnerability in n/a, published on 28 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-30570 in the wild and no public exploit code. Affected product: n/a. 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-2023-30570/ (Markdown: https://insights.sbomify.com/CVE-2023-30570/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-30570 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-30570 - OSV: https://osv.dev/vulnerability/CVE-2023-30570 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-30570/ Summaries are generated and may contain mistakes; the official description above is the record.