# CVE-2023-22043: Other in Java SE JDK and JRE > An unauthenticated attacker can modify or delete critical data in Java SE via JavaFX, affecting client-side deployments running untrusted code. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Jul 2023 - **Updated:** 13 Feb 2025 - **Also known as:** BIT-java-2023-22043, BIT-java-min-2023-22043, BIT-jre-2023-22043, DEBIAN-CVE-2023-22043, GHSA-grjf-4ggg-f6cm, MINI-gvxh-mp25-jm45, UBUNTU-CVE-2023-22043 ## What is CVE-2023-22043? CVE-2023-22043 is a medium-severity vulnerability in Oracle Jdk, published on 18 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Vulnerability in Oracle Java SE (component: JavaFX). The supported version that is affected is Oracle Java SE: 8u371. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N). ## Which versions are affected by CVE-2023-22043? 3 open source packages ship an affected version, including java, java-min and jre. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `java` | Bitnami | All versions | 1.8.0, 8.0.381 | | `java-min` | Bitnami | All versions | 1.8.0, 8.0.381 | | `jre` | Bitnami | All versions | 1.8.0, 8.0.381 | Products: Oracle Jdk, Oracle Jre. ## How do I fix CVE-2023-22043? Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.381. ## Is CVE-2023-22043 being exploited? There is no known exploitation of CVE-2023-22043 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Jdk - [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild) - [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild) - [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0) - [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0) - [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-22043 and fix it if it is affected. What it is: CVE-2023-22043 is a medium-severity vulnerability in Oracle Jdk, published on 18 Jul 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-22043 in the wild and no public exploit code. Affected packages and fixed versions: - java (Bitnami): affected all versions; fixed in 1.8.0, 8.0.381 - java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.381 - jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.381 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-22043/ (Markdown: https://insights.sbomify.com/CVE-2023-22043/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22043 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22043 - OSV: https://osv.dev/vulnerability/CVE-2023-22043 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-22043/ Summaries are generated and may contain mistakes; the official description above is the record.