This is a major challenge. We can never really say we can definitely support EoL products with EoL versions of BigFix, but if it is trivial to extend support and others can demonstrate how, then great, please help us enhance our templates to do so.
Amazon Correto JRE/JDK8 does seem to go further back in support than Azul or AdoptOpenJDK but it seems to have more requirements for VC++ redist? Correto doesn’t go back further than v8.
We have also been trying to look for solutions here.
Until you know you have something that breaks, this is the right approach if you want to get things mitigated in a timely fashion.
Unless the system is critical to the point of life or death or the system impacts many other systems (domain controller, LDAP, SAN, etc) then it might be better to break it than to have a remote code exploit remain open.
And if something does break, do you roll back everything? or maybe only 1 or 2 things broke and you go fix them by trying to update the JAR to 2.17 or look for vendor patches or something else. Or just roll back that one app.
And if you do find something that breaks, please please please tell us all here so everyone can know about it!