HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
randorisec
CVE-2022-34918-LPE-PoC
C2022–2022
randorisec / CVE-2022-34918-LPE-PoC

CVE-2022-34918-LPE-PoC

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
243GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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, 5:04:57 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 hour2 dated mentions

Observed mentions: 2022-07-21 11:58:02 UTC to 2022-07-21 12:53:11 UTC.

012022-07-21 11:00:00 UTC to 2022-07-21 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 21, 11:002022-07-21 12:00:00 UTC to 2022-07-21 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 21, 12: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
Jul 21, 11:002022-07-21 11:00:00 UTC2022-07-21 12:00:00 UTC101
Jul 21, 12:002022-07-21 12:00:00 UTC2022-07-21 13:00:00 UTC101

What Hacker News says

2 sources
Looking at the exploit code [1], sadly, you don't... They're using the fact that you can become "root" in a new namespace. So you need cgroups. After that, you're free to change NFTables in that namespace. I was just playing around with this: $ unshare -r --net --user capsh --print and comparing it to $ sudo capsh --print Both give you all caps. Exploiting a parser bug in NFTables doesn't require access to the main namespace; just something to get past the initial cap checks. (IIUC.) Edit: the commands above were run on Ubuntu 21.10. [1] https://github.com/randorisec/CVE-2022-34918-LPE-PoC/blob/ma...
In A Crack in the Linux Firewall

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.