HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
NCSC-NL
log4shell
Python2021–2021
NCSC-NL / log4shell · Archived

log4shell

Operational information regarding the log4shell vulnerabilities in the Log4j logging library.

4Distinct people
4Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Operational information regarding the log4shell vulnerabilities in the Log4j logging library.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval4 dated mentions

Observed mentions: 2021-12-12 21:36:35 UTC to 2021-12-15 08:11:58 UTC.

012021-12-12 21:00:00 UTC to 2021-12-13 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 12, 21:002021-12-13 00:00:00 UTC to 2021-12-13 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-13 03:00:00 UTC to 2021-12-13 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-13 06:00:00 UTC to 2021-12-13 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-13 09:00:00 UTC to 2021-12-13 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-13 12:00:00 UTC to 2021-12-13 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2021-12-13 15:00:00 UTC to 2021-12-13 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-13 18:00:00 UTC to 2021-12-13 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-13 21:00:00 UTC to 2021-12-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-14 00:00:00 UTC to 2021-12-14 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 14, 00:002021-12-14 03:00:00 UTC to 2021-12-14 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-14 06:00:00 UTC to 2021-12-14 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-14 09:00:00 UTC to 2021-12-14 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-14 12:00:00 UTC to 2021-12-14 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-14 15:00:00 UTC to 2021-12-14 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-14 18:00:00 UTC to 2021-12-14 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-14 21:00:00 UTC to 2021-12-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-12-15 00:00:00 UTC to 2021-12-15 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-15 03:00:00 UTC to 2021-12-15 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-15 06:00:00 UTC to 2021-12-15 09:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 15, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 12, 21:002021-12-12 21:00:00 UTC2021-12-13 00:00:00 UTC110
Dec 13, 00:002021-12-13 00:00:00 UTC2021-12-13 03:00:00 UTC000
Dec 13, 03:002021-12-13 03:00:00 UTC2021-12-13 06:00:00 UTC000
Dec 13, 06:002021-12-13 06:00:00 UTC2021-12-13 09:00:00 UTC000
Dec 13, 09:002021-12-13 09:00:00 UTC2021-12-13 12:00:00 UTC000
Dec 13, 12:002021-12-13 12:00:00 UTC2021-12-13 15:00:00 UTC110
Dec 13, 15:002021-12-13 15:00:00 UTC2021-12-13 18:00:00 UTC000
Dec 13, 18:002021-12-13 18:00:00 UTC2021-12-13 21:00:00 UTC000
Dec 13, 21:002021-12-13 21:00:00 UTC2021-12-14 00:00:00 UTC000
Dec 14, 00:002021-12-14 00:00:00 UTC2021-12-14 03:00:00 UTC000
Dec 14, 03:002021-12-14 03:00:00 UTC2021-12-14 06:00:00 UTC000
Dec 14, 06:002021-12-14 06:00:00 UTC2021-12-14 09:00:00 UTC000
Dec 14, 09:002021-12-14 09:00:00 UTC2021-12-14 12:00:00 UTC000
Dec 14, 12:002021-12-14 12:00:00 UTC2021-12-14 15:00:00 UTC000
Dec 14, 15:002021-12-14 15:00:00 UTC2021-12-14 18:00:00 UTC000
Dec 14, 18:002021-12-14 18:00:00 UTC2021-12-14 21:00:00 UTC000
Dec 14, 21:002021-12-14 21:00:00 UTC2021-12-15 00:00:00 UTC101
Dec 15, 00:002021-12-15 00:00:00 UTC2021-12-15 03:00:00 UTC000
Dec 15, 03:002021-12-15 03:00:00 UTC2021-12-15 06:00:00 UTC000
Dec 15, 06:002021-12-15 06:00:00 UTC2021-12-15 09:00:00 UTC110

What Hacker News says

4 sources
Site author here. Thanks for helping to get the word out - every bit may help someone. While I consider my page to provide useful color, and I validate and summarize and cache info updates locally to add value ... it won't scale for long. It's really a stopgap - to buy defenders time until better efforts emerge. A few efforts likely to become higher leverage than mine, because they can be driven by pull requests: * https://github.com/NCSC-NL/log4shell - already quite comprehensive * Whatever CISA may spin up - https://github.com/cisagov/log4j-affected-db * Kevin Beaumont (@GossiTheDog) - turns out he worked with CISA on this That being said, I'll keep working on mine as long as it still provides value; updates/corrections welcome.
In Log4Shell Log4j vulnerability (CVE-2021-44228) – cheat-sheet reference guide

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.