CVE-2021-44228-Scanner VS log4shelldetect

Take a look at https://github.com/logpresso/CVE-2021-44228-Scanner as another option

I found a scanner on Github that checks for Logj4 vulnerabilities that has versions for several different OSs including Linux but I am not familiar enough with Linux on Synology to run this on my own. I might figure it out if I spend a couple of hours but it would be really helpful to me, and I presume, others here if someone with the skills could respond with a short list of what to do to get this running, preferably as a one-time scheduled task or series of them if it takes that, rather than SSH'ing to the box.

Dell proposes Logpresso's log4j scan tool (https://github.com/logpresso/CVE-2021-44228-Scanner/releases) to mitigate vulnerabilities for various product lines, until they released actual fixes (various are still pending, so we only have the scan tool).

Peculiarly Dell for some of their data protection products also seems to advice to use a 3rd party scan tool to mitigate against certain issues in <2.14 and 2.15 log4j using log4j-scan from Logpresso https://github.com/logpresso/CVE-2021-44228-Scanner, as far as I can see a Korean company? Would have imagined Dell would also have some developers being able to write something? But that's just me...

I'm not sure what you mean. You can deploy a built binary over your network and run it on all your servers. For example: curl -sSL https://github.com/1lann/log4shelldetect/releases/download/v0.0.2/log4shelldetect_0.0.2_Linux_x86_64.tar.gz | tar -C /tmp/ -zxf - log4shelldetect && /tmp/log4shelldetect -mode list /path/to/scan 2>/dev/null would download and extract the prebuilt binary to /tmp, and run it scanning at /path/to/scan, only outputting paths to potentially vulnerable .jars and ignoring warnings. You can replace the URL with your own build or distribute your own build as you wish.