Yes, should be good to go. The last version of Ignition that used log4j was 7.8, and it used something like log4j version 1.2.x, which isn’t affected by this CVE.
Those who snoop around may find an artifact called log4j-over-slf4j, but this just a bridge that let us move from log4j to slf4j/logback without modifying every single file that had used a log4j logger.
I would like to be 100% certain on this topic…can this please be clarified? The following library is running on our test and production Ignition servers. It is not part of this CVE?