Impact of the CVE-2022-23302, CVE-2022-23305 and CVE-2022-23307

Products

• CA Service Desk Manager
• CA Service Management - Service Desk Manager

Issue/Introduction

Is Service Desk Management (SDM) impacted by following vulnerabilities?

CVE-2022-23302: JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data

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

CVE-2022-23307: CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a compnent of Apache Log4j 1.2.x where the same issue exists.

Environment

CA Service Desk Manager 17.2 and higher

Resolution

Those vulnerabilities do not impact CA SDM. 

CVE-2022-23302: JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data
--->
This vulnerability is exploitable, only when it uses JMSSink, CA SDM is NOT using JMSSink.

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.
--->
This vulnerability is exploitable, only when it uses JDBCAppender, CA SDM is NOT using JDBCAppender.

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.
--->
This vulnerability is exploitable, only when it uses SocketAppender, CA SDM is NOT using SocketAppender.