I recognize this probably isn't helpful on its face, but the best way to think of it is: if it's a Java app (or heck even possibly just an app running on the JVM) that uses the most recent major version (2.x before 2.15.0, the patch) of the most common logging logic, it's affected.
And that list in the enterprise space gets exceptionally long. Maybe not so much on client machines, but servers/etc absolutely.
Even companies not known for using Java for their own apps are probably relying on appliances or systems which run their own vulnerable Java apps.
Though even that long list is missing many. I have lots of emails in my inbox from various software vendors that are NOT listed in that Gist.
It's probably easier to compile a list of software you use that uses java, then the short of those projects that DON'T use log4j.
https://community.kronos.com/s/feed/0D54M00004wJCdJSAW?langu...
Companies likely only started IR in the last week. Breach notifications, which only a minority of companies will bother to send out, will be a few weeks away at the earliest.
I suspect we'll be patching quickly before Christmas.