Debian has issued an advisory on December 27: https://www.debian.org/security/2019/dsa-4596 The issues are fixed upstream in 9.0.30: http://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.29 http://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.30 Mageia 7 is also affected.
Whiteboard: (none) => MGA7TOO
Hmmm it fails to build on both Cauldron and mga7, related to current java-1.8.0-openjdk?
CC: (none) => geiger.david68210
CC: (none) => nicolas.salguero
Fedora has updated to 9.0.30: https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/QKC3AMZQVWY34PC24RYAAO4N57HWS6QG/
SUSE has issued an advisory for this on January 7: http://lists.suse.com/pipermail/sle-security-updates/2020-January/006307.html
Status comment: (none) => Fixed upstream in 9.0.30
As I said it fails to build with: compile: [javac] Compiling 1735 source files to /home/iurt/rpmbuild/BUILD/apache-tomcat-9.0.30-src/output/classes [javac] /home/iurt/rpmbuild/BUILD/apache-tomcat-9.0.30-src/java/org/apache/jasper/compiler/JDTCompiler.java:329: error: cannot find symbol [javac] CompilerOptions.VERSION_12); [javac] ^ [javac] symbol: variable VERSION_12 [javac] location: class CompilerOptions [javac] /home/iurt/rpmbuild/BUILD/apache-tomcat-9.0.30-src/java/org/apache/jasper/compiler/JDTCompiler.java:400: error: cannot find symbol [javac] CompilerOptions.VERSION_12); [javac] ^ [javac] symbol: variable VERSION_12 [javac] location: class CompilerOptions [javac] /home/iurt/rpmbuild/BUILD/apache-tomcat-9.0.30-src/java/org/apache/jasper/compiler/JDTCompiler.java:402: error: cannot find symbol [javac] CompilerOptions.VERSION_12); [javac] ^ [javac] symbol: variable VERSION_12 [javac] location: class CompilerOptions [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] 3 errors BUILD FAILED
Suggested advisory: ======================== The updated packages fix security vulnerabilities: 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. (CVE-2019-12418) When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability. (CVE-2019-17563) References: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563 https://www.debian.org/security/2019/dsa-4596 http://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.29 http://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.30 https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/QKC3AMZQVWY34PC24RYAAO4N57HWS6QG/ http://lists.suse.com/pipermail/sle-security-updates/2020-January/006307.html ======================== Updated packages in core/updates_testing: ======================== tomcat-9.0.30-1.mga7 tomcat-admin-webapps-9.0.30-1.mga7 tomcat-docs-webapp-9.0.30-1.mga7 tomcat-jsvc-9.0.30-1.mga7 tomcat-jsp-2.3-api-9.0.30-1.mga7 tomcat-lib-9.0.30-1.mga7 tomcat-servlet-4.0-api-9.0.30-1.mga7 tomcat-el-3.0-api-9.0.30-1.mga7 tomcat-webapps-9.0.30-1.mga7 from SRPMS: tomcat-9.0.30-1.mga7.src.rpm
Version: Cauldron => 7Whiteboard: MGA7TOO => (none)CVE: (none) => CVE-2019-12418, CVE-2019-17563Assignee: java => qa-bugsStatus: NEW => ASSIGNED
Ref to bug 23045 Comment 8 for tests and bug 24799 Comment 15 for configuration changes. Browse http://localhost:8080/sample and http://localhost:8080/examples and click the links. Also browse http://localhost:8080 and log into the 'manager app' with the credentials just configured with manager-gui role. All work OK
CC: (none) => herman.viaeneWhiteboard: (none) => MGA7-64-OK
Validating. Advisory in Comment 5.
CC: (none) => andrewsfarm, sysadmin-bugsKeywords: (none) => validated_update
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2020-0054.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED