Communications Instant Messaging Server vulnerabilities

6 known vulnerabilities in Communications Instant Messaging Server from Oracle. 6 are rated high or critical, and 3 have been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.

Latest first

• 8.8 High severity

  Apache Log4j 1.x: Deserialization of Untrusted Data

  CVE-2022-23307Jan 18, 2022ApacheEPSS 54.4%

  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.

• 9.8 Critical severity

  Apache Log4j 1.x: Improper Neutralization of Special Elements used in an SQL Command

  CVE-2022-23305Jan 18, 2022ApacheEPSS 66.5%

  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

• 8.8 High severity

  Apache Log4j 1.x: Deserialization of Untrusted Data

  CVE-2022-23302Jan 18, 2022ApacheEPSS 63.8%

  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 Topi

• 9.8 Critical severity

  Apache Tomcat Improper Privilege Management Exploited

  CVE-2020-1938Feb 24, 2020ApacheEPSS 99.3%

  When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attac

• 8.1 High severity

  Apache Tomcat Remote Code Execution Exploited

  CVE-2017-12617Oct 4, 2017ApacheEPSS 100%

  When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default servlet to false) it was possible to upload a JSP file

• 9.8 Critical severity

  Apache Tomcat Remote Code Execution Exploited

  CVE-2016-8735Apr 6, 2017ApacheEPSS 90.3%

  Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x before 9.0.0.M12 if JmxRemoteLifecycleListener is used and an attacker can reach JMX ports. The issue exists because this list