{"answers":{"affected":"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.","exploited":"There is no known exploitation of CVE-2022-23302 in the wild and no public exploit code.","fix":"Product is end of life, replace it.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-23302 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-23302 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- log4j:log4j (Maven): affected all versions up to 1.2.17; no fix listed\n- log4j:log4j (Maven): affected all versions up to 1.2.17; no fix listed\n- org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions up to 2.0; no fix listed\n- org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions up to 2.0; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-23302/ (Markdown: https://insights.sbomify.com/CVE-2022-23302/index.md)","id":"CVE-2022-23302","markdown":"https://insights.sbomify.com/CVE-2022-23302/index.md","name":"CVE-2022-23302","record":{"aliases":["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"],"analysis":{"component_type":"library","fix_type":"end_of_life","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Java logging library","requires_auth":"low_privilege","summary":"Attackers can achieve remote code execution via JNDI injection in Log4j 1.x JMSSink if configured, requiring migration to Log4j 2.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"log4j","vendor":"apache"},{"product":"brocade_sannav","vendor":"broadcom"},{"product":"snapmanager","vendor":"netapp"},{"product":"advanced_supply_chain_planning","vendor":"oracle"},{"product":"business_intelligence","vendor":"oracle"},{"product":"business_process_management_suite","vendor":"oracle"},{"product":"communications_eagle_ftp_table_base_retrieval","vendor":"oracle"},{"product":"communications_instant_messaging_server","vendor":"oracle"},{"product":"communications_messaging_server","vendor":"oracle"},{"product":"communications_network_integrity","vendor":"oracle"},{"product":"communications_offline_mediation_controller","vendor":"oracle"},{"product":"communications_unified_inventory_management","vendor":"oracle"},{"product":"e-business_suite_cloud_manager_and_cloud_backup_module","vendor":"oracle"},{"product":"enterprise_manager_base_platform","vendor":"oracle"},{"product":"financial_services_revenue_management_and_billing_analytics","vendor":"oracle"},{"product":"healthcare_foundation","vendor":"oracle"},{"product":"hyperion_data_relationship_management","vendor":"oracle"},{"product":"hyperion_infrastructure_technology","vendor":"oracle"},{"product":"identity_management_suite","vendor":"oracle"},{"product":"identity_manager_connector","vendor":"oracle"},{"product":"jdeveloper","vendor":"oracle"},{"product":"middleware_common_libraries_and_tools","vendor":"oracle"},{"product":"mysql_enterprise_monitor","vendor":"oracle"},{"product":"tuxedo","vendor":"oracle"},{"product":"weblogic_server","vendor":"oracle"},{"product":"reload4j","vendor":"qos"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Deserialization of untrusted data in JMSSink in Apache Log4j 1.x","id":"CVE-2022-23302","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"broadcom:brocade_sannav","products":["broadcom:brocade_sannav","netapp:snapmanager","oracle:business_intelligence","oracle:communications_instant_messaging_server","oracle:communications_unified_inventory_management","oracle:enterprise_manager_base_platform","oracle:hyperion_data_relationship_management","oracle:hyperion_infrastructure_technology","oracle:mysql_enterprise_monitor","oracle:weblogic_server"],"type":"deserialization","year":"2022"},"n_packages":4,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-23303"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.2.17"],"package":"log4j:log4j","purl":null,"source":"GHSA-w9p3-5cr8-m3jj"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.2.17"],"package":"log4j:log4j","purl":"pkg:maven/log4j/log4j","source":"GHSA-w9p3-5cr8-m3jj"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.0"],"package":"org.zenframework.z8.dependencies.commons:log4j-1.2.17","purl":null,"source":"GHSA-w9p3-5cr8-m3jj"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.0"],"package":"org.zenframework.z8.dependencies.commons:log4j-1.2.17","purl":"pkg:maven/org.zenframework.z8.dependencies.commons/log4j-1.2.17","source":"GHSA-w9p3-5cr8-m3jj"}],"prev":{"headline":"HEVC Video Extensions Remote Code Execution Vulnerability","id":"CVE-2022-23301"},"products":["Apache Log4j 1.x"],"published":"2022-01-18","related":[{"cvss_score":10,"headline":"Apache Log4j2 Remote Code Execution","id":"CVE-2021-44228","kev_date_added":"2021-12-10","published":"2021-12-10"},{"cvss_score":9,"headline":"Apache Log4j2 Deserialization of Untrusted Data","id":"CVE-2021-45046","kev_date_added":"2023-05-01","published":"2021-12-14"},{"cvss_score":9.8,"headline":"SQL injection in JDBC Appender in Apache Log4j V1","id":"CVE-2022-23305","kev_date_added":null,"published":"2022-01-18"},{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in Log4j","id":"CVE-2017-5645","kev_date_added":null,"published":"2017-04-17"},{"cvss_score":7.5,"headline":"Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender","id":"CVE-2023-26464","kev_date_added":null,"published":"2023-03-10"},{"cvss_score":7.5,"headline":"Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2","id":"CVE-2021-4104","kev_date_added":null,"published":"2021-12-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["Apache Software Foundation"]},"summary":"Attackers can achieve remote code execution via JNDI injection in Log4j 1.x JMSSink if configured, requiring migration to Log4j 2.","url":"https://insights.sbomify.com/CVE-2022-23302/"}