Apache Tomcat CVE-2024-52316 and WHD 12.8.3 HF3

This has flagged as a vulnerability in the version of tomcat used bundled with Web Help Desk, at least as of 12.8.3. HF3.

Out of an abundance of caution, even though Apache is reporting this as low, I contacted support about upgrading just the bundled tomcat application out of cycle with the rest of the product to a non-affected version.  Initially, I received some steps on how to do so, however using anything newer than the bundled version causes the application to crash at start.  Validated this again with support and received a secondary response that it is a known issue and that upgrading the bundled version is not supported at this time due to something in newer releases breaking WHD.

I did get clarification that engineering is working on a solution to this CVE internally to WHD until they or Apache can sort out what is broken in the newer releases.  

Parents
  • Can confirm 12.8.4 addressed this CVE:

    CVE-2024-52316 Unchecked Error Condition vulnerability in Apache Tomcat Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. 9.8 Critical
Reply
  • Can confirm 12.8.4 addressed this CVE:

    CVE-2024-52316 Unchecked Error Condition vulnerability in Apache Tomcat Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue. 9.8 Critical
Children
No Data