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)
|
History
07 Nov 2023, 03:39
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2021-12-28 20:15
Updated : 2024-02-28 18:48
NVD link : CVE-2021-44832
Mitre link : CVE-2021-44832
CVE.ORG link : CVE-2021-44832
JSON object : View
Products Affected
cisco
- cloudcenter
apache
- log4j
oracle
- flexcube_private_banking
- primavera_gateway
- primavera_unifier
- health_sciences_data_management_workbench
- communications_offline_mediation_controller
- retail_order_broker
- primavera_p6_enterprise_project_portfolio_management
- product_lifecycle_analytics
- policy_automation_for_mobile_devices
- weblogic_server
- siebel_ui_framework
- communications_interactive_session_recorder
- communications_brm_-_elastic_charging_engine
- retail_assortment_planning
- communications_diameter_signaling_router
- policy_automation
- retail_xstore_point_of_service
- retail_fiscal_management
fedoraproject
- fedora
debian
- debian_linux