Amazon Linux AMI 2: CVE-2019-12418: Security patch for tomcat (Multiple Advisories)
Description
When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.
Solution(s)
- amazon-linux-ami-2-upgrade-tomcat
- amazon-linux-ami-2-upgrade-tomcat-admin-webapps
- amazon-linux-ami-2-upgrade-tomcat-docs-webapp
- amazon-linux-ami-2-upgrade-tomcat-el-2-2-api
- amazon-linux-ami-2-upgrade-tomcat-el-3-0-api
- amazon-linux-ami-2-upgrade-tomcat-javadoc
- amazon-linux-ami-2-upgrade-tomcat-jsp-2-2-api
- amazon-linux-ami-2-upgrade-tomcat-jsp-2-3-api
- amazon-linux-ami-2-upgrade-tomcat-jsvc
- amazon-linux-ami-2-upgrade-tomcat-lib
- amazon-linux-ami-2-upgrade-tomcat-servlet-3-0-api
- amazon-linux-ami-2-upgrade-tomcat-servlet-3-1-api
- amazon-linux-ami-2-upgrade-tomcat-servlet-4-0-api
- amazon-linux-ami-2-upgrade-tomcat-webapps
- Lightweight Endpoint Agent
- Live Dashboards
- Real Risk Prioritization
- IT-Integrated Remediation Projects
- Cloud, Virtual, and Container Assessment
- Integrated Threat Feeds
- Easy-to-Use RESTful API
- Automation-Assisted Patching
- Automated Containment
With Rapid7 live dashboards, I have a clear view of all the assets on my network, which ones can be exploited, and what I need to do in order to reduce the risk in my environment in real-time. No other tool gives us that kind of value and insight.
– Scott Cheney, Manager of Information Security, Sierra View Medical Center