Log4j
Named by 7 kept items in this workspace.
6 items name it under affected products and 1 under classification.technologies.
Search every workspace for Log4j. It matches the name as written, so it can find other things that share it.
The items that name it 7
Log4Shell, historical comparison
Dependency-based vulnerability (e.g. log4j-style issue); found by VM tools scanning disk for the .jar file; real fix is appsec ticket or patching the parent application
affected by CVE-2021-44228 (Log4Shell), commonly a transitive dependency
Cited as example: vulnerability lives in a specific JNDI lookup method; if application code never calls that method, the CVE is not exploitable even though the vulnerable package is in the dependency tree
Example cited: when Log4J vulnerability hit, companies with products written in C had no Log4J exposure but still fielded customer calls, illustrating signal-to-noise problem VEX addresses
Log4Shell
All technologies in this workspace.