Good find. As of yet, I haven't been able to tell if our build has file-inspect or not which is where the vuln is. I've tried to put in different options for it in the config and some pass and some error out from here: https://www.snort.org/faq/readme-file . The readme says the code was experimental.
If we do have file-inspect maybe we can turn off it's dependency like the frag3 preprocessor. I haven't been able to find much info on it except v18.104.22.168 patches it. I'll try to continue to research or if someone familiar with determining if our build was compiled with the file inspect flag.