Forum Discussion

SPATIALinfo_Pty_1's avatar
SPATIALinfo_Pty_1
Visitor
3 years ago
Solved

Is Alertsite affected by the Log4J vulnerability?

Hi 
I would like to know if Alertsite application is affected by the Log4J vulnerability issue and if it is has a patch has been release ?

 

Thanks in advance

 

Frank

  • sonya_m's avatar
    sonya_m
    3 years ago

    Hi SPATIALinfo_Pty_1 ,

     

    The Apache Log4j2 Remote Code Execution (RCE) Vulnerabilities - CVE-2021-44228 and CVE-2021-45046 have been mitigated or remediated on SmartBear-managed cloud products. If you are on an on-premise version or a customized version, please reach out to our support team at https://support.smartbear.com for further information.

     

    Apache recently announced that the fix to address CVE-2021-44228 (upgrading Log4j to at least version 2.15.0) is not complete if non-default or custom configurations are used. SmartBear products remain unaffected with this new information. SmartBear does not use the non-default configurations and the residual risk is low in using the 2.15.0 version of Log4j.

     

    Many SmartBear products are already using Log4j 2.16.0. Out of an abundance of caution, SmartBear products not already using 2.16 will update to this version during the next available release.

4 Replies

Sort By
  • SJeffries's avatar
    SJeffries
    Staff
    3 years ago

    Public locations have been patched. Private locations are only impacted in very rare circumstances; when endpoints being tested are vulnerable and other internal insecure assets are in play. A release to mitigate the rare circumstances is being developed now. Feel free to contact Customer Care directly if you are still concerned

  • sonya_m's avatar
    sonya_m
    SmartBear Alumni (Retired)
    3 years ago

    Hi SPATIALinfo_Pty_1 ,

     

    The Apache Log4j2 Remote Code Execution (RCE) Vulnerabilities - CVE-2021-44228 and CVE-2021-45046 have been mitigated or remediated on SmartBear-managed cloud products. If you are on an on-premise version or a customized version, please reach out to our support team at https://support.smartbear.com for further information.

     

    Apache recently announced that the fix to address CVE-2021-44228 (upgrading Log4j to at least version 2.15.0) is not complete if non-default or custom configurations are used. SmartBear products remain unaffected with this new information. SmartBear does not use the non-default configurations and the residual risk is low in using the 2.15.0 version of Log4j.

     

    Many SmartBear products are already using Log4j 2.16.0. Out of an abundance of caution, SmartBear products not already using 2.16 will update to this version during the next available release.

    • knight2628's avatar
      knight2628
      New Member
      3 years ago

      Hi,

       

      Has Alert site taken the proper steps to update to 2.17?

       

      Thank you, 

       

      knight2628

      • SJeffries's avatar
        SJeffries
        Staff
        3 years ago

        A new release for Private Locations is being reviewed now by Quality Assurance. The new release will mitigates all potential vulnerabilities regarding log4j. All private instances where this is a concern will be able to upgrade to this version once released. It will be released very soon