What is the severity of USN-4251-1?

The severity of USN-4251-1 is considered high due to the potential for local attackers to gain complete control over the Tomcat instance.

How do I fix USN-4251-1?

To fix USN-4251-1, update the affected packages to version 8.0.32-1ubuntu1.11 on Ubuntu 16.04.

Who is affected by USN-4251-1?

Users running Tomcat 8 on Ubuntu 16.04 are affected by USN-4251-1.

What causes the vulnerability USN-4251-1?

USN-4251-1 is caused by improper handling of the RMI registry when configured with the JMX Remote Lifecycle Listener.

Is there a workaround for USN-4251-1 prior to patching?

Disabling the JMX Remote Lifecycle Listener can mitigate the risk associated with USN-4251-1 until a patch is applied.

Vulnerability/
USN-4251-1

27/1/2020

USN-4251-1: Tomcat vulnerabilities

First published: Mon Jan 27 2020(Updated: )

It was discovered that Tomcat incorrectly handled the RMI registry when configured with the JMX Remote Lifecycle Listener. A local attacker could possibly use this issue to obtain credentials and gain complete control over the Tomcat instance. (CVE-2019-12418) It was discovered that Tomcat incorrectly handled FORM authentication. A remote attacker could possibly use this issue to perform a session fixation attack. (CVE-2019-17563)

Affected Software	Affected Version	How to fix
All of
ubuntu/libtomcat8-java	<8.0.32-1ubuntu1.11	8.0.32-1ubuntu1.11
Ubuntu Linux	=16.04
All of
ubuntu/tomcat8	<8.0.32-1ubuntu1.11	8.0.32-1ubuntu1.11
Ubuntu Linux	=16.04

Never miss a vulnerability like this again

Reference Links

Child vulnerabilities

(Contains the following vulnerabilities)

Frequently Asked Questions

What is the severity of USN-4251-1?
The severity of USN-4251-1 is considered high due to the potential for local attackers to gain complete control over the Tomcat instance.
How do I fix USN-4251-1?
To fix USN-4251-1, update the affected packages to version 8.0.32-1ubuntu1.11 on Ubuntu 16.04.
Who is affected by USN-4251-1?
Users running Tomcat 8 on Ubuntu 16.04 are affected by USN-4251-1.
What causes the vulnerability USN-4251-1?
USN-4251-1 is caused by improper handling of the RMI registry when configured with the JMX Remote Lifecycle Listener.
Is there a workaround for USN-4251-1 prior to patching?
Disabling the JMX Remote Lifecycle Listener can mitigate the risk associated with USN-4251-1 until a patch is applied.

agent/last-modified-date
agent/references
agent/title
agent/severity
agent/softwarecombine
agent/type
agent/description
agent/first-publish-date
agent/event
agent/trending
agent/source
agent/tags
collector/usn
source/Ubuntu
agent/software-canonical-lookup
agent/software-canonical-lookup-request
package-manager/ubuntu
vendor/ubuntu
canonical/ubuntu linux
version/ubuntu linux/16.04

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.