[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7XSgw98CHeliIOhvPUje2DTI6s9ZXV9IdFjothnfwU0":3,"g5a-family:oracle\u002Fcommunications_instant_messaging_server":146,"g5a-ex:oracle\u002Fcommunications_instant_messaging_server@*":147},{"success":4,"data":5},true,{"product":6,"versions":42,"topVulnerabilitiesByEpss":53,"kevVulnerabilities":111,"seoMetadata":124,"meta":143},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":41},"oracle","communications_instant_messaging_server",10,57,3,"2022-01-18",[14,18,22,24,26,30,33,35,37,39],{"version":15,"cve_count":16,"kev_count":16,"has_kev":17},"10.0",0,false,{"version":19,"cve_count":20,"kev_count":21,"has_kev":4},"10.0.1",4,2,{"version":23,"cve_count":11,"kev_count":16,"has_kev":17},"10.0.1.2.0",{"version":25,"cve_count":20,"kev_count":16,"has_kev":17},"10.0.1.3.0",{"version":27,"cve_count":28,"kev_count":29,"has_kev":4},"10.0.1.4.0",19,1,{"version":31,"cve_count":32,"kev_count":16,"has_kev":17},"10.0.1.5.0",26,{"version":34,"cve_count":16,"kev_count":16,"has_kev":17},"8.0",{"version":36,"cve_count":21,"kev_count":16,"has_kev":17},"8.1",{"version":38,"cve_count":16,"kev_count":16,"has_kev":17},"9.0.1",{"version":40,"cve_count":16,"kev_count":16,"has_kev":17},"9.0.2","Communications Instant Messaging Server by Oracle is a technology product with 10 tracked versions and 57 known security vulnerabilities including 3 CISA Known Exploited Vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[43,44,45,46,47,48,49,50,51,52],{"version":15,"cve_count":16,"kev_count":16,"has_kev":17},{"version":19,"cve_count":20,"kev_count":21,"has_kev":4},{"version":23,"cve_count":11,"kev_count":16,"has_kev":17},{"version":25,"cve_count":20,"kev_count":16,"has_kev":17},{"version":27,"cve_count":28,"kev_count":29,"has_kev":4},{"version":31,"cve_count":32,"kev_count":16,"has_kev":17},{"version":34,"cve_count":16,"kev_count":16,"has_kev":17},{"version":36,"cve_count":21,"kev_count":16,"has_kev":17},{"version":38,"cve_count":16,"kev_count":16,"has_kev":17},{"version":40,"cve_count":16,"kev_count":16,"has_kev":17},[54,62,69,74,79,85,92,96,100,105],{"cveId":55,"description":56,"publishedDate":57,"cvssScore":58,"cvssVersion":59,"severity":60,"isKev":4,"epssScore":61},"CVE-2017-12617","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 to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.","2017-10-04",8.1,"v3.1","High",0.99968,{"cveId":63,"description":64,"publishedDate":65,"cvssScore":66,"cvssVersion":59,"severity":67,"isKev":4,"epssScore":68},"CVE-2020-1938","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 attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.","2020-02-24",9.8,"Critical",0.9927,{"cveId":70,"description":71,"publishedDate":72,"cvssScore":66,"cvssVersion":59,"severity":67,"isKev":4,"epssScore":73},"CVE-2016-8735","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 listener wasn't updated for consistency with the CVE-2016-3427 Oracle patch that affected credential types.","2017-04-06",0.90338,{"cveId":75,"description":76,"publishedDate":77,"cvssScore":66,"cvssVersion":59,"severity":67,"isKev":17,"epssScore":78},"CVE-2017-5645","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 deserialized, can execute arbitrary code.","2017-04-17",0.89792,{"cveId":80,"description":81,"publishedDate":82,"cvssScore":83,"cvssVersion":59,"severity":60,"isKev":17,"epssScore":84},"CVE-2020-13935","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. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service.","2020-07-14",7.5,0.86608,{"cveId":86,"description":87,"publishedDate":88,"cvssScore":89,"cvssVersion":59,"severity":90,"isKev":17,"epssScore":91},"CVE-2021-33037","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 used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP\u002F1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.","2021-07-12",5.3,"Medium",0.74667,{"cveId":93,"description":94,"publishedDate":12,"cvssScore":66,"cvssVersion":59,"severity":67,"isKev":17,"epssScore":95},"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 executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. 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.",0.66537,{"cveId":97,"description":98,"publishedDate":82,"cvssScore":83,"cvssVersion":59,"severity":60,"isKev":17,"epssScore":99},"CVE-2020-13934","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\u002F1.1 processor after the upgrade to HTTP\u002F2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.",0.64124,{"cveId":101,"description":102,"publishedDate":12,"cvssScore":103,"cvssVersion":59,"severity":60,"isKev":17,"epssScore":104},"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 result in remote code execution in a similar fashion to CVE-2021-4104. Note 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.",8.8,0.63556,{"cveId":106,"description":107,"publishedDate":108,"cvssScore":109,"cvssVersion":59,"severity":60,"isKev":17,"epssScore":110},"CVE-2020-9484","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 is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter=\"null\" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.","2020-05-20",7,0.5552,[112,117,120],{"cveId":70,"description":71,"publishedDate":72,"cvssScore":66,"severity":67,"isKev":4,"epssScore":73,"cisaVulnName":113,"cisaDateAdded":114,"cisaShortDescription":115,"cisaRequiredAction":116},"Apache Tomcat Remote Code Execution Vulnerability","2023-05-12","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.","Apply updates per vendor instructions.",{"cveId":55,"description":56,"publishedDate":57,"cvssScore":58,"severity":60,"isKev":4,"epssScore":61,"cisaVulnName":113,"cisaDateAdded":118,"cisaShortDescription":119,"cisaRequiredAction":116},"2022-03-25","When running Apache Tomcat, it is possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.",{"cveId":63,"description":64,"publishedDate":65,"cvssScore":66,"severity":67,"isKev":4,"epssScore":68,"cisaVulnName":121,"cisaDateAdded":122,"cisaShortDescription":123,"cisaRequiredAction":116},"Apache Tomcat Improper Privilege Management Vulnerability","2022-03-03","Apache Tomcat treats Apache JServ Protocol (AJP) connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited.",{"title":125,"metaDescription":126,"keywords":127,"structuredData":128},"Communications Instant Messaging Server by Oracle - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Communications Instant Messaging Server by Oracle covering 10 versions with 57 tracked vulnerabilities including 2 critical and 1 high-severity issues and 3 CISA KEV vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Communications Instant Messaging Server vulnerabilities, Communications Instant Messaging Server security, Communications Instant Messaging Server CVE, Oracle Communications Instant Messaging Server, Communications Instant Messaging Server threat intelligence, Oracle security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking, Communications Instant Messaging Server KEV, Communications Instant Messaging Server exploited vulnerabilities",{"@context":129,"@type":130,"name":131,"description":126,"url":132,"manufacturer":133,"applicationCategory":137,"softwareVersion":138,"mainEntity":139},"https:\u002F\u002Fschema.org","SoftwareApplication","Communications Instant Messaging Server","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Foracle\u002Fcommunications_instant_messaging_server",{"@type":134,"name":135,"url":136},"Organization","Oracle","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Foracle","Security Software","10 versions tracked",{"@type":140,"name":141,"description":142,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Communications Instant Messaging Server Security Vulnerabilities","Security vulnerabilities affecting Communications Instant Messaging Server by Oracle",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":144,"apiVersion":145},"2026-10-17T12:49:21.633Z","3.0",[],{"rows":148,"total":11,"capped":17,"failed":16},[149,153,157],{"cveId":70,"name":113,"severity":67,"cvss":66,"added":114,"epss":73,"published":150,"ranges":151,"checked":4,"hits":152,"covers":17},"2017-04-06T21:59:00.243",[19],[],{"cveId":55,"name":113,"severity":60,"cvss":58,"added":118,"epss":61,"published":154,"ranges":155,"checked":4,"hits":156,"covers":17},"2017-10-04T01:29:02.12",[19],[],{"cveId":63,"name":121,"severity":67,"cvss":66,"added":122,"epss":68,"published":158,"ranges":159,"checked":4,"hits":160,"covers":17},"2020-02-24T22:15:12.057",[27],[]]