VNX: VNXe2 (VNXe3200 and VNXe1600) and VNX2 False Positive Vulnerabilities for Apache Log4j

Summary: This article provides a list of security vulnerabilities that cannot be exploited on Dell EMC VNXe2 (VNXe3200 and VNXe1600) products and VNX2 series VNX5200, VNX5400, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600,VNX8000 products, but which may be identified by security scanners. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Security Article Type

Security KB

CVE Identifier

CVE-2020-9488, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307

Issue Summary

See the 'Recommendation' section below for details on each CVE.

Recommendations

The vulnerabilities listed in the table below are in order by the date on which Dell EMC Engineering determined that the VNXe3200 (Version no 3.1.17.10223906), VNXe1600 (Version no. 3.1.16.10224109) and VNX2 series VNX5200, VNX5400, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600 and VNX8000 (Block 5.33.021.5.266, File 8.1.21.266) was not vulnerable.
 
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.
  1. The SmtpAppender requires SSL configuration element to specify a trust store, host name verification, and a key store, so that smtps connections can be further configured. This uses the SSL configuration element.
  2. SmtpAppender class requires configuration to be done for setting up SSL configuration and connections. This setup and configurations do not come configured by default for log4j bundle.
  3. For VNXe2 and VNX2 series product we do not configure, setup and consume SmtpAppender class.
 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.
  1. JMSSink is a simple application that consumes logging events sent by a JMSAppender.
  2. This flaw only affects applications which are specifically configured to use JMSSink, which is not the default.
  3. For VNXe2, the Log4j configuration file has write permission for only c4 user (which is like a admin user), for VNX2, the Log4j configuration file has write permission only for root user.  As in both the products, the Log4j configuration file is not having world write permission, it is difficult for an attacker to modify this file.
 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.
  1. The JDBCAppender is used for sending log events to a database.
  2. By default, the log4j.xml file does not have JDBC configured.
  3. JDBCAppender class is not consumed in code for VNX2 and VNXe2 products.
 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.
  1. Apache Chainsaw is a supporting application for Log4j. It is a GUI-based log viewer that can read log files in Log4j’s XMLLayout format.
  2. By default, it listens for LoggingEvent objects sent using the SocketAppender and displays them in a table. The events can be filtered based on: Level, Thread name, Logger, Message, and NDC.
  3. Log4j is not configured to use Chainsaw by default.
  4. VNX2 and VNXe2 code does not consume Chainsaw APIs.
  5. The log4j.xml configuration file does not have Chainsaw configured in VNX2 and VNXe2 product series.
  6. Chainsaw listens to the logging objects sent on SocketAppender. VNX2 and VNXe2 does not have SocketAppender configured for Log4j.
  

Legal Disclaimer

Affected Products

VNX5200, VNX5400, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600, VNX8000, VNXe1 Series, VNX/VNXe

Products

VNXe1000 Series, VNXe1600, VNXe2 Series, VNXe3200
Article Properties
Article Number: 000197378
Article Type: Security KB
Last Modified: 04 Nov 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.