# CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x > Attackers can achieve remote code execution via JNDI injection in Log4j 1.x JMSSink if configured, requiring migration to Log4j 2. - **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:** 18 Jan 2022 - **Updated:** 27 May 2026 - **Also known as:** CLEANSTART-2026-VM68422, CLSA-2026-1787932767, DEBIAN-CVE-2022-23302, GHSA-w9p3-5cr8-m3jj, MINI-mjcc-h5m5-cqh5, MINI-wq68-jfxv-2cxv, ROOT-APP-MAVEN-CVE-2022-23302, UBUNTU-CVE-2022-23302 ## What is CVE-2022-23302? CVE-2022-23302 is a high-severity unsafe deserialization vulnerability in Broadcom Brocade Sannav, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2022-23302? 4 open source packages ship an affected version, including log4j:log4j and org.zenframework.z8.dependencies.commons:log4j-1.2.17. It affects 26 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `log4j:log4j` | Maven | All versions to 1.2.17 | None | | `log4j:log4j` | Maven | All versions to 1.2.17 | None | | `org.zenframework.z8.dependencies.commons:log4j-1.2.17` | Maven | All versions to 2.0 | None | | `org.zenframework.z8.dependencies.commons:log4j-1.2.17` | Maven | All versions to 2.0 | None | Products: Apache Log4j, Broadcom Brocade Sannav, Netapp Snapmanager, Oracle Advanced Supply Chain Planning, Oracle Business Intelligence, Oracle Business Process Management Suite, Oracle Communications Eagle Ftp Table Base Retrieval, Oracle Communications Instant Messaging Server, Oracle Communications Messaging Server, Oracle Communications Network Integrity, Oracle Communications Offline Mediation Controller, Oracle Communications Unified Inventory Management, Oracle E-Business Suite Cloud Manager and Cloud Backup Module, Oracle Enterprise Manager Base Platform, Oracle Financial Services Revenue Management and Billing Analytics, Oracle Healthcare Foundation, Oracle Hyperion Data Relationship Management, Oracle Hyperion Infrastructure Technology, Oracle Identity Management Suite, Oracle Identity Manager Connector and 6 more. ## How do I fix CVE-2022-23302? Product is end of life, replace it. ## Is CVE-2022-23302 being exploited? There is no known exploitation of CVE-2022-23302 in the wild and no public exploit code. ## Other vulnerabilities in Broadcom Brocade Sannav - [CVE-2021-44228](https://insights.sbomify.com/CVE-2021-44228/): Apache Log4j2 Remote Code Execution (critical 10.0, exploited in the wild) - [CVE-2021-45046](https://insights.sbomify.com/CVE-2021-45046/): Apache Log4j2 Deserialization of Untrusted Data (critical 9.0, exploited in the wild) - [CVE-2022-23305](https://insights.sbomify.com/CVE-2022-23305/): SQL injection in JDBC Appender in Apache Log4j V1 (critical 9.8) - [CVE-2017-5645](https://insights.sbomify.com/CVE-2017-5645/): Deserialization of Untrusted Data in Log4j (critical 9.8) - [CVE-2023-26464](https://insights.sbomify.com/CVE-2023-26464/): Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-23302 and fix it if it is affected. What it is: CVE-2022-23302 is a high-severity unsafe deserialization vulnerability in Broadcom Brocade Sannav, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-23302 in the wild and no public exploit code. Affected packages and fixed versions: - log4j:log4j (Maven): affected all versions up to 1.2.17; no fix listed - log4j:log4j (Maven): affected all versions up to 1.2.17; no fix listed - org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions up to 2.0; no fix listed - org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions up to 2.0; no fix listed 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-2022-23302/ (Markdown: https://insights.sbomify.com/CVE-2022-23302/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23302 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23302 - OSV: https://osv.dev/vulnerability/CVE-2022-23302 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-23302/ Summaries are generated and may contain mistakes; the official description above is the record.