Hi @verdonv1,
Java is used for the analytics mechanism so, unless you’re OK with not having this data, it is necessary.
CE 5 [that’s Eagle, actually, Falcon was version 6] is very very old indeed. The analytics code included in your version may run correctly with Java 1.7 but I can’t guarantee it. I’m quite positive it will fail with 1.8. You can switch the versions [using the alternatives mechanism], wait 24 hours to allow all the DWH scripts to run and verify there are no errors in /opt/kaltura/dwh/logs.
If there are issues, you can again use the alternatives mechanism to switch back [it basically changes where the /etc/alternatives/java symlink points to].
That said, running such an old version, I imagine Java is not the only vulnerable component. The Kaltura Server relies on many third party components [PHP, Apache, OpenSSL, etc, etc] and if you haven’t upgraded these from the official repos then your machine is potentially subjected to other exploits. Of course, we also made several security enhancements in our own code base since CE 5 was released [over 6 years ago].
While the migration path from the pre-RPM version is not as straightforward and smooth as with the RPMs, I highly recommend you clone your production machine[s], perform the needed steps, test and, once everything is OK, replace your current production instance[s].
For instructions on how to migrate pre-RPM versions, see my reply here: