Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Configuration 6 (hide)
|
Information
Published : 2021-12-28 12:15
Updated : 2022-08-08 18:24
NVD link : CVE-2021-44832
Mitre link : CVE-2021-44832
JSON object : View
CWE
CWE-20
Improper Input Validation
Products Affected
oracle
- siebel_ui_framework
- primavera_unifier
- primavera_p6_enterprise_project_portfolio_management
- policy_automation_for_mobile_devices
- retail_order_broker
- communications_offline_mediation_controller
- health_sciences_data_management_workbench
- communications_diameter_signaling_router
- weblogic_server
- policy_automation
- communications_interactive_session_recorder
- flexcube_private_banking
- product_lifecycle_analytics
- retail_xstore_point_of_service
- primavera_gateway
- communications_brm_-_elastic_charging_engine
- retail_fiscal_management
- retail_assortment_planning
fedoraproject
- fedora
debian
- debian_linux
cisco
- cloudcenter
apache
- log4j