Communications Instant Messaging Server vulnerabilitiesAnd the versions its exploited flaws hit.
Communications Instant Messaging Server is made by Oracle. We track 57 published vulnerabilities in it, across 10 versions. 3 of them are on the list of flaws known to be exploited, the newest added on 12 May 2023. If you run Communications Instant Messaging Server, check your version against the exploited flaws below and patch those first.
The most recent Communications Instant Messaging Server flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023. We keep watching the known-exploited list.
Which versions of Communications Instant Messaging Server do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2016-8735Exploited list, 12 May 2023
Apache Tomcat Remote Code Execution Vulnerability
10.0.1 - CVE-2017-12617Exploited list, 25 Mar 2022
Apache Tomcat Remote Code Execution Vulnerability
10.0.1 - CVE-2020-1938Exploited list, 3 Mar 2022
Apache Tomcat Improper Privilege Management Vulnerability
10.0.1.4.0
Which Communications Instant Messaging Server vulnerabilities are being exploited?
3 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8Apache Tomcat Remote Code Execution Vulnerability
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports.
- 8.1Apache Tomcat Remote Code Execution Vulnerability
When running Apache Tomcat, it is possible to upload a JSP file to the server via a specially crafted request.
- 9.8Apache Tomcat Improper Privilege Management Vulnerability
Apache Tomcat treats Apache JServ Protocol (AJP) connections as having higher trust than, for example, a similar HTTP connection.
Which Communications Instant Messaging Server flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
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.
- >99%
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat.
- 90%CVE-2017-5645Critical
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when...
- 87%CVE-2020-13935High
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104.
- 75%CVE-2021-33037Medium
Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when...
- 67%CVE-2022-23305Critical
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.
- 64%CVE-2020-13934High
An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2.
- 64%CVE-2022-23302High
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...
- 56%CVE-2020-9484High
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server...
Running Communications Instant Messaging Server? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports. This CVE exists because this listener wasn't updated for consistency with the Oracle patched issues for CVE-2016-3427 which affected credential types.
- Matched to
- Communications Instant Messaging Server on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 57 published vulnerabilities listed under the name Communications Instant Messaging Server, across 10 versions. The most recent Communications Instant Messaging Server flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023.
3 are on the list of flaws known to be exploited. The most recently added are CVE-2016-8735, CVE-2017-12617 and CVE-2020-1938.
Each flaw names its own versions, usually as ranges. The newest, CVE-2016-8735, affects 10.0.1. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Communications Instant Messaging Server. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.