# CVE-2023-39913: Apache UIMA Java SDK Deserialization of Untrusted Data, Improper Input Validation vulnerability > Attackers can execute arbitrary code via unsafe deserialization of binary CAS formats in Apache UIMA Java SDK, particularly when using Vinci services or custom CasIOUtils implementations. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 8 Nov 2023 - **Updated:** 13 Feb 2025 - **Also known as:** GHSA-5r8j-qmcm-7g7q, openSUSE-SU-2024:13471-1 ## What is CVE-2023-39913? CVE-2023-39913 is a high-severity unsafe deserialization vulnerability in Apache UIMA Java SDK CPE, published on 8 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Deserialization of Untrusted Data, Improper Input Validation vulnerability in Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK.This issue affects Apache UIMA Java SDK: before 3.5.0. Users are recommended to upgrade to version 3.5.0, which fixes the issue. There are several locations in the code where serialized Java objects are deserialized without verifying the data. This affects in particular: * the deserialization of a Java-serialized CAS, but also other binary CAS formats that include TSI information using the CasIOUtils class; * the CAS Editor Eclipse plugin which uses the the CasIOUtils class to load data; * the deserialization of a Java-serialized CAS of the Vinci Analysis Engine service which can receive using Java-serialized CAS objects over network connections; * the CasAnnotationViewerApplet and the CasTreeViewerApplet; * the checkpointing feature of the CPE module. Note that the UIMA framework by default does not start any remotely accessible services (i.e. Vinci) that would be vulnerable to this issue. A user or developer would need to make an active choice to start such a service. However, users or developers may use the CasIOUtils in their own applications and services to parse serialized CAS data. They are affected by this issue unless they ensure that the data passed to CasIOUtils is not a serialized Java object. When using Vinci or using CasIOUtils in own services/applications, the unrestricted deserialization of Java-serialized CAS files may allow arbitrary (remote) code execution. As a remedy, it is possible to set up a global or context-specific ObjectInputFilter (cf. https://openjdk.org/jeps/290  and  https://openjdk.org/jeps/415 ) if running UIMA on a Java version that supports it. Note that Java 1.8 does not support the ObjectInputFilter, so there is no remedy when running on this out-of-support platform. An upgrade to a recent Java version is strongly recommended if you need to secure an UIMA version that is affected by this issue. To mitigate the issue on a Java 9+ platform, you can configure a filter pattern through the "jdk.serialFilter" system property using a semicolon as a separator: To allow deserializing Java-serialized binary CASes, add the classes: * org.apache.uima.cas.impl.CASCompleteSerializer * org.apache.uima.cas.impl.CASMgrSerializer * org.apache.uima.cas.impl.CASSerializer * java.lang.String To allow deserializing CPE Checkpoint data, add the following classes (and any custom classes your application uses to store its checkpoints): * org.apache.uima.collection.impl.cpm.CheckpointData * org.apache.uima.util.ProcessTrace * org.apache.uima.util.impl.ProcessTrace_impl * org.apache.uima.collection.base_cpm.SynchPoint Make sure to use "!*" as the final component to the filter pattern to disallow deserialization of any classes not listed in the pattern. Apache UIMA 3.5.0 uses tightly scoped ObjectInputFilters when reading Java-serialized data depending on the type of data being expected. Configuring a global filter is not necessary with this version. Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2023-39913? 2 open source packages ship an affected version, including org.apache.uima:uimaj. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.uima:uimaj` | Maven | All versions | 3.5.0 | | `org.apache.uima:uimaj` | Maven | All versions | 3.5.0 | Products: Apache Uimaj. ## How do I fix CVE-2023-39913? Upgrade org.apache.uima:uimaj to 3.5.0 or later. ## Is CVE-2023-39913 being exploited? There is no known exploitation of CVE-2023-39913 in the wild and no public exploit code. ## Other vulnerabilities in Apache UIMA Java SDK CPE - [CVE-2022-32287](https://insights.sbomify.com/CVE-2022-32287/): Apache UIMA prior to 3.3.1 has a path traversal vulnerability when extracting (PEAR) archives (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-39913 and fix it if it is affected. What it is: CVE-2023-39913 is a high-severity unsafe deserialization vulnerability in Apache UIMA Java SDK CPE, published on 8 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-39913 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.uima:uimaj (Maven): affected all versions; fixed in 3.5.0 - org.apache.uima:uimaj (Maven): affected all versions; fixed in 3.5.0 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-39913/ (Markdown: https://insights.sbomify.com/CVE-2023-39913/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-39913 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-39913 - OSV: https://osv.dev/vulnerability/CVE-2023-39913 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-39913/ Summaries are generated and may contain mistakes; the official description above is the record.