Is com.guicedee.services:log4j-core 1.0 vulnerable?
Maven · 91 releases from 1.0.2 to 1.0.20.2 · latest com.guicedee.services:log4j-core is 1.2.2.1-jre17 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. com.guicedee.services:log4j-core 1.0.20.2, the last 1.0 release, is affected by 1 known security advisory (1 critical), including CVE-2021-44228. At least one has no fixed release yet.
Is your project on an affected com.guicedee.services:log4j-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting com.guicedee.services:log4j-core 1.0.20.2
Remote code injection in Log4j
- Affected
- <=1.2.1.2-jre17
- Fixed in
- No fix released
Every com.guicedee.services:log4j-core 1.0.x release
Affected: 1.0.8.1 to 1.0.20.2. Latest com.guicedee.services:log4j-core: 1.2.2.1-jre17.
| Version | Known advisories |
|---|---|
| com.guicedee.services:log4j-core 1.0.20.2 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.20.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.20 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.13 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.11 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.10 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.9 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.6 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.5 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.4 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.3 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.2 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.19 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.18.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.18 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.17.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.17 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.16 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.15.5 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.15.4 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.15.2 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.15.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.15 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.14.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.14 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.13.5 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.13.4 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.13.3 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.13.2 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.13.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.13 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.12.5 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.12.4 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.12.3 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.12.2 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.12.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.12 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.11.7 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.11.5 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.11 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.10.4 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.10.3 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.10.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.10 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.9.14 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.9.13 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.9.11 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.9.10 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.9.2 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.9.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.9 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.18 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.16 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.12 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.5 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.4 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.3 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.2 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.0.8.1 | CVE-2021-44228 |
Which of your client projects are still on com.guicedee.services:log4j-core 1.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact com.guicedee.services:log4j-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other com.guicedee.services:log4j-core versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.