News for hackers. Stuff that matters.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by tptacek on Tuesday November 17, 2026 @05:49PM (#50539373)
On a simple count like that you could probably beat SQLI on "Javascript prototype pollution", too. But those are 5 classes of vulnerabilities with wildly different impacts, and platform-level SQLI is actually pretty rare.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by iLoveOncall on Tuesday November 17, 2026 @06:26PM (#50539675)
Yeah move the goalpost. Calif.io employee I presume.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by thephyber on Tuesday November 17, 2026 @06:41PM (#50539833)
Do you not know who tptacek is?

He's pretty famous in cybersecurity and on HN as a poster.

Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by tptacek on Tuesday November 17, 2026 @06:59PM (#50540019)
Not so much that I'm above criticism, I'm clearly not, so much as how funny it is to suggest "coworker of Thai Duong, Tavis Ormandy, Michal Zalewski, Dion Blazakis, and Stefan Esser" is a dunk. Shit, now I kind of do want to be a Calif.io employee.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by thephyber on Tuesday November 17, 2026 @07:07PM (#50540087)
I didn't mean to imply that you are above criticism.

More that you aren't just the average HN NPC and that your comments are usually high SNR and well informed.

Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by ranger_danger on Tuesday November 17, 2026 @07:13PM (#50540147)
I have seen their comments across this site for a very long time. Unfortunately I do not respect or put any stock in what they say, because of how unbelievably rude and dogmatic they are, and always have been.

"As a rule, strong feelings about issues do not emerge from deep understanding."

Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by tptacek on Tuesday November 17, 2026 @07:52PM (#50540445)
Well that hurts my feelings but also you're right: nobody should respect or put any stock into what I say because of my identity or status (whatever that might be).
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by iLoveOncall on Wednesday November 18, 2026 @03:32AM (#50543494)
All I see is someone writing a series of bullshit and when proven wrong moves the goalpost?
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by cjbprime on Tuesday November 17, 2026 @06:32PM (#50539741)
Is "the most common class of vulnerability" not supposed to be measured by a simple count? It's the blog post's own plain language and it doesn't say anything about impact.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by deathanatos on Tuesday November 17, 2026 @06:42PM (#50539842)
> Is "the most common class of vulnerability" not supposed to be measured by a simple count?

Trivially yes? It'd be a rate of some ilk at least. Upthread, to their credit, was a "score" of undefined nature.

But also, more upthread is talking about "memory corruption", which is going to include far more than just CWE-787. CWEs are a bit weird, and things I'd include in a loose colloquail definition like that would include stack based overflows, heap based overflows (which are for some reason different in CWE land), "classic buffer overflows" (CWE-120, again, their wording), out of bounds writes, OoB reads, null derefs, and use-after-free. All separate CWEs.

Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by tptacek on Tuesday November 17, 2026 @06:46PM (#50539885)
It's just a category error comparison. SQLI is a web pest vulnerability; memory corruption RCE is a vulnerability research vulnerability. They're different disciplines. Web SQLI vulnerabilities are usually application-code-specific (not just "application specific", but with a specific origin in a mistake made in application code). Big ticket vulnerability research publications are generally platform vulnerabilities; one specific coding mistake impacting thousands or millions of installs.

It's very weird to look at a memory corruption RCE and say SQLI is "more common". On typical web targets, memory corruption RCE is basically unheard of (and SQLI is not the most common sev:hi vulnerability; SSRF probably outranks it).

These are just vulnerability researchers talking like vulnerability researchers.

Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by ranger_danger on Tuesday November 17, 2026 @07:07PM (#50540099)
It sounds like there's more fundamentally a disagreement on what that phrase actually means to them in the first place.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by cjbprime on Tuesday November 17, 2026 @07:39PM (#50540337)
> For example, one of many different ways of looking at this issue: perhaps by "...vulnerabilities on the Internet" they could have meant in reference to reported CVEs, [..]

The CWE count is by reference to reported CVEs. If they meant that, they were wrong.