Article Number: 000197378
Security KB
CVE-2020-9488, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307
See the 'Recommendation' section below for details on each CVE.
Third-party Component | CVE IDs | Summary of Vulnerability | Reason why Product is not Vulnerable | Date Determined False Positive |
SMTP Appender | CVE-2020-9488 | Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This may potentially allow an SMTPS connection to be intercepted by a man-in-the-middle attack which may leak any log messages that are sent through that appender. |
|
February 28, 2022 |
JMSSink | CVE-2022-23302 | 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 may result in remote code execution in a similar fashion to CVE-2021-4104. Note that 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. |
|
January 27, 2022 |
JDBCAppender | CVE-2022-23305 | By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be run. |
|
February 28, 2022 |
Apache Chainsaw | CVE-2022-23307 | CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw v2.0, Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists. |
|
The information should be read and used to assist in avoiding situations that may arise from the problems described herein. Dell Technologies distributes Security Advisories, Security Notices and Informational articles to bring important security information to the attention of users of the affected product(s). Dell Technologies assesses the risk based on an average of risks across a diverse set of installed systems and may not represent the actual risk to your local installation and individual environment. It is recommended that all users determine the applicability of this information to their individual environments and take appropriate actions. The information set forth herein is provided "as is" without warranty of any kind. Dell Technologies expressly disclaims all warranties, either express or implied, including the warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Dell Technologies, its affiliates or suppliers, be liable for any damages whatsoever arising from or related to the information contained herein or actions that you decide to take based thereon, including any direct, indirect, incidental, consequential, loss of business profits or special damages, even if Dell Technologies, its affiliates or suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation shall apply to the extent permissible under law.
VNX5200, VNX5400, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600, VNX8000, VNXe1 Series, VNX/VNXe
VNXe1000 Series, VNXe1600, VNXe2 Series, VNXe3200
15 Mar 2022
1
Security KB