HN Simulatornew | past | comments | lists | submit | CER10TY's commentslogin

All I'm seeing is *******

oh sweet, so when I type hunter2, all you see is ****? thats really clever

Considering OpenSSL 4.2 is the first proper 4.x LTS release, I think most distros will still be on OpenSSL 3.x so not impacted.

Bleeding edge distros like Arch/Fedora are already on 4.x, so they'll be impacted, but they should also receive a patch relatively quickly.


You can freely specify the encoding when sending multipart/form-data POST since Rails respects the charset attribute in Content-Type, eg Content-Type: text/plain; charset=Windows-1252

So you have to convert ISO-2022-JP, for example? That sounds like a disaster waiting to happen.

Clients have to do the same with server responses.

Relevant article about that here: https://www.sonarsource.com/blog/encoding-differentials-why-...

Browsers stopped auto-detecting ISO-2022-JP for this reason.


Isn't this delay pretty standard nowadays, due to the sheer number of submissions? It's also not like you can just hop onto another CNA (eg GitLab) if the repo is on GitHub, as it's out of scope for other CNAs.

Well the fix for this seemingly already landed in the repo last week: https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

Given how common it's become to constantly scan popular repos for n-days, I expect someone will have already picked it up and started work on an exploit. The workaround for this (disabling HTTP/2) is also comparatively easy to what we had with PHP2Shell just a few weeks back, so I think it makes sense to release this.


> Given how common it's become to constantly scan popular repos for n-days

We have people doing this on my side project and then reporting the fixed issues to try and get CVE 'credit'. Tiring.


To be fair, the warning to either take down websites or patch immediately on release came from the people who've been working on this for months (or those with advance notices like CERTs), not out of nowhere. People just took it down pre-emptively since exploit attempts (whether working or not) popped up in logs way before the patch was released, but it also took forever until the fix actually landed downstream after the advisories were released.


I think people are just latching onto the post that hit the front page earlier today about it being non-trivial to exploit, combined with the fact that there seem to be about a billion PoC out there, most of which don't work.


Right, that's what's worrying me. It is not interesting that the most widely circulated public POC/demos don't work. All you should care about is the (currently) non-public POCs that do work, of which there are apparently several.


The most direct exploit requires a compromised supply chain which ranks it about as dangerous as your usual dependency exploits.


Say what you will about OpenAI, Wiz etc but if OpenAI, Wiz, Cloudflare, the PHP Foundation and pretty much every CERT out there together recommend to take down PHP apps and patch immediately then I'm very much inclined to follow that advice.

Due to the insane media coverage there'll of course be a deluge of PoCs, most of which won't work. But constantly refreshing Twitter to see whether there's a working PoC is not a good use of time nor a great security strategy.


I think this is just false? Are we playing some kind of weird game of telephone? Is the term "direct exploit" doing way more work in that sentence than you mean it to?


The alternative route through the web forms requires the absence of ASLR. So you need to spam the endpoint, like a lot. You can probably mitigate at the edge (CDNs) or perhaps at the reverse proxy level (NGINX) through e.g. rate limiting. More of a web version of row hammer then some sort of trivial SQL injection attack that works consistently.

Maybe a LAMP stack on an extremely ancient version of Linux is vulnerable out of the box. Quit the fear mongering please, you do the security community no favors.


Are they, though? I seriously doubt some sysadmin is going to look at this and say "Maintainers said to patch, but clearly _this guy_ knows better, so I won't."

Besides, he's got a point. The initial PoC that kept popping up on Mastodon (the ones he linked in the post as well) simply didn't work. One of them even posted an updated exploit later that still didn't work, but supposedly meant the vulnerability went from CVSS 10 to CVSS 4.


I know someone who hacked his own site using the exploit and managed to obtain a database dump.


Lots of places where Senior just means 3+ YOE and anything more than that has even fancier titles like "Staff" or "Principal".


I see. Yeah it basically means ~7 YoE at my shop. Was 5, but we started delaying the promotion when we started belt-tightening in 23.

FWIW I'm at a Visual Studio shop and grep competency is pretty rare across the board.


„Let me ask my LLM“


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: