Looks like Kalutra is using log4j and the version installed (2.11.1) used by elasticsearch match with a vulnerable one.
@jess do you know if Kalutra is impacted by this issue ? Is there a recommended/official way to patch this without breaking something ?
Version: Kaltura CE 16.14.0
Many thanks
3 posts - 2 participants