190
you are viewing a single comment's thread
view the rest of the comments
[-] f314@lemmy.world 54 points 2 days ago

WHY do all new vulnerabilities have to use this inane naming scheme? These are grown-up problems. Can we use grown-up names?

If someone finds another vulnerability in Nginx that gives root access, will it be called NGINX3root or NGINX2root2?

(Yes, I know this is a petty complaint)

[-] gdog05@lemmy.world 19 points 1 day ago

NGINX2:AI Boogaloo

[-] Tolookah@discuss.tchncs.de 45 points 2 days ago
[-] BigBrownBeaver@lemmy.world 20 points 2 days ago

2nginx2root2you

[-] xavier666@lemmy.umucat.day 9 points 1 day ago
[-] Guiorgy@lemmy.ml 4 points 1 day ago

Nah, only Microsoft vulnerabilities can end with 36x (it was only 365 before though)

[-] 123@programming.dev 2 points 1 day ago

Better reserve that 35X name next year the way things are progressing.

[-] Morphit@feddit.uk 1 points 1 day ago
[-] Willdrick@lemmy.world 24 points 1 day ago

We've been swarmed with these for the last few months, but the catchy names are useful to spread awareness easier. You'll never see a headline on mainstream news "CVE-20261213-69420" but maybe you'll see Spectre, log4j, or my new fave *sshole

[-] barnacles@lemmy.zip 7 points 1 day ago* (last edited 1 day ago)

Heartbleed was an absolute masterpiece of branding

[-] phx@lemmy.world 4 points 1 day ago

Yeah, I highly doubt many people remember CVE-2021-44228 but anyone in tech around the end of 2021 will sure AF "log4j Christmas".

Similarly, CVE-2017-0144 doesn't really ring in the ears. MS17-010 might be somewhat more familiar, but EternalBlue (the related NSA exploit) is what most in the industry remember

[-] eleijeep@piefed.social 15 points 2 days ago

You're right, at the least the name should have the year in it so that we know if it's a new vulnerability or an old one.

And since a product can have multiple vulnerabilities in the same year we should have a number that increments with each new vulnerability found.

Also, since one vulnerability can affect multiple products (eg. a vulnerability in a library), we can't use the product names to identify the vulnerability (as that could be quite a long list). We will just use the acronym for our naming scheme so that we can distinguish our list of numbers from other lists of numbers like book ISBNs or ICQ numbers.

We could call our naming scheme the Cool Vulnerability Eponym.

So the vulnerability name would end up as something like CVE-2026-123456.

[-] f314@lemmy.world 9 points 2 days ago

Lol, nice backronym! CVEs are great! They’re not very scannable in headlines, though. For that I would actually prefer product name to be involved. Just maybe not written as a Fast and Furious movie title.

[-] GreenKnight23@lemmy.world 8 points 1 day ago

Nginx4 GettinGRooted

[-] Ooops@feddit.org 6 points 1 day ago

will it be called NGINX3root

Only if the next one targets http3 instead of http2 😉

[-] WhyJiffie@sh.itjust.works 2 points 1 day ago

this one is targeting http3 too

[-] Ooops@feddit.org 1 points 1 day ago* (last edited 1 day ago)

It's explicitly exploiting the http2 flow control and neither 1.1 (the link above even suggests deactivating http2 as a temporary measure) nor –afaik– http3 (which works differently just by design principle) are affected.

[-] WhyJiffie@sh.itjust.works 1 points 1 day ago
[-] Ooops@feddit.org 1 points 21 hours ago

I assumed we are talking about the title specifically.

Crashing your service with an exploit depending "on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled" that "may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution" may be a critical issues, too, but is not exactly the same thing as a proven way to get root access.

[-] WhyJiffie@sh.itjust.works 1 points 44 minutes ago* (last edited 44 minutes ago)

edit: this was a duplicate

[-] WhyJiffie@sh.itjust.works 1 points 46 minutes ago

this CVE is also listed on the page linked in the post. and the root privileges are gained through a linux vulnerability, the nginx cves dont give root they just allow arbitrary code execution

[-] boonhet@sopuli.xyz 9 points 2 days ago

This is a much more descriptive name than SPECTRE or MELTDOWN though. I'll take this scheme any day of the week.

[-] CosmicTurtle0@lemmy.dbzer0.com 5 points 2 days ago

They've done studies that more attention is given to vulnerabilities that have catchy names (since they can be reported on) than CVE-2026-42069.

[-] Jesus_666@lemmy.world 4 points 2 days ago

2NGINX2root, followed by NGINX root: Tokyo Drift.

[-] tburkhol@lemmy.world 3 points 1 day ago

I suspect it's because most of the new crop of vulnerabilities have been discovered by AI companies and those companies need press coverage. Seems like all of these 'x2root' issues are, at best, dependent on uncommon or ill-advised setups, or depend on extremely unlikely events actually to get RCE.

I'm on the verge of just ignoring them all. Which, maybe that's phase 1 of the plan to pwn the entire internet.

this post was submitted on 19 Nov 2026
190 points (99.0% liked)

Selfhosted

63939 readers
1197 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS