imPC@ndo IT

Tracker / CVE-2022-23302

CVE-2022-23302

High 8.8

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.

Affected products and versions

apache log4j · 1.0.1 → 1.2.17
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_offline_mediation_controller · … → 12.0.0.4.4
oracle communications_unified_inventory_management
oracle e-business_suite_cloud_manager_and_cloud_backup_module
oracle e-business_suite_cloud_manager_and_cloud_backup_module · … → 2.2.1.1.1
oracle enterprise_manager_base_platform
oracle financial_services_revenue_management_and_billing_analytics
oracle healthcare_foundation
oracle hyperion_data_relationship_management · … → 11.2.8.0
oracle hyperion_infrastructure_technology · … → 11.2.8.0
oracle identity_management_suite
oracle identity_manager_connector
oracle jdeveloper
oracle middleware_common_libraries_and_tools
oracle mysql_enterprise_monitor · … → 8.0.29
oracle tuxedo
oracle weblogic_server
qos reload4j · … → 1.2.18.1

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References