# CVE-2023-28205: Apple Multiple Products WebKit Use-After-Free > Attackers can execute arbitrary code by tricking users into visiting malicious web content in Safari or WebKit-based apps. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 10 Apr 2023 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 10 Apr 2023 - **Updated:** 21 Oct 2025 - **Also known as:** ALSA-2023:1918, ALSA-2023:1919, DEBIAN-CVE-2023-28205, GHSA-6qjh-p74q-89mv, RHSA-2023:1918, RHSA-2023:1919, RLSA-2023:1918, RLSA-2023:1919, UBUNTU-CVE-2023-28205 ## What is CVE-2023-28205? CVE-2023-28205 is a high-severity use after free vulnerability in Apple Ipados, published on 10 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description A use after free issue was addressed with improved memory management. This issue is fixed in Safari 16.4.1, iOS 15.7.5 and iPadOS 15.7.5, iOS 16.4.1 and iPadOS 16.4.1, macOS Ventura 13.3.1. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2023-28205? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `webkit2gtk3` | AlmaLinux:8 | All versions | 2.36.7-1.el8_7.3 | | `webkit2gtk3-devel` | AlmaLinux:8 | All versions | 2.36.7-1.el8_7.3 | | `webkit2gtk3-jsc` | AlmaLinux:8 | All versions | 2.36.7-1.el8_7.3 | | `webkit2gtk3-jsc-devel` | AlmaLinux:8 | All versions | 2.36.7-1.el8_7.3 | | `webkit2gtk3` | AlmaLinux:9 | All versions | 2.36.7-1.el9_1.3 | | `webkit2gtk3-devel` | AlmaLinux:9 | All versions | 2.36.7-1.el9_1.3 | | `webkit2gtk3-jsc` | AlmaLinux:9 | All versions | 2.36.7-1.el9_1.3 | | `webkit2gtk3-jsc-devel` | AlmaLinux:9 | All versions | 2.36.7-1.el9_1.3 | | `webkit2gtk3` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-devel-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-jsc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-jsc-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-jsc-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3-jsc-devel-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-jsc` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-jsc-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-jsc-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3-jsc-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.36.7-1.el9_1.3 | | `webkit2gtk3` | Rocky Linux:8 | All versions | 0:2.36.7-1.el8_7.3 | | `webkit2gtk3` | Rocky Linux:9 | All versions | 0:2.36.7-1.el9_1.3 | Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Safari. ## How do I fix CVE-2023-28205? Apply the vendor's patch. US federal agencies must fix it by 1 May 2023. ## Is CVE-2023-28205 being exploited? Yes. Attackers have exploited CVE-2023-28205 in the wild since at least 10 Apr 2023. Public exploit code: - PoC CVE-2023-28205: Apple WebKit Use-After-Free Vulnerability (github_poc): https://github.com/ntfargo/uaf-2023-28205 - PoC CVE-2023-28205: Apple WebKit Use-After-Free Vulnerability (github_poc): https://github.com/seregonwar/uaf-2023-28205 ## Other vulnerabilities in Apple Ipados - [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild) - [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild) - [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild) - [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild) - [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-28205 and fix it if it is affected. What it is: CVE-2023-28205 is a high-severity use after free vulnerability in Apple Ipados, published on 10 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: Yes. Attackers have exploited CVE-2023-28205 in the wild since at least 10 Apr 2023. Affected product: Apple Ipados. 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-28205/ (Markdown: https://insights.sbomify.com/CVE-2023-28205/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-28205 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-28205 - OSV: https://osv.dev/vulnerability/CVE-2023-28205 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-28205/ Summaries are generated and may contain mistakes; the official description above is the record.