zlacker

[return to "Critical RCE Vulnerabilities in React and Next.js"]
1. _pdp_+Uc[view] [source] 2025-12-03 16:58:16
>>gonepi+(OP)
I don't have time to look into it right now (def later)!

However, I was curious to see if github copilot can reverse engineer it based on the latest commits and seems that what it is saying aligns with both advisories. It pointed out that it has to do with circular reference handling which sounds to me something that can be easily overlooked.

While this analysis might be completely off, the simple fact that I could get even this information without much efforts is mind-boggling. With better setup it might be able to get more.

With AI now being common place, coordinated timely disclosure is even more important considering the stakes. It is theoretically possible to get an exploit working within minutes. Considering that we see one of these major vulnerabilities annually (and it seems to me around the same time of the year) a bad actor can easily capitalise on the opportunities when presented.

◧◩
2. intern+Sh[view] [source] 2025-12-03 17:19:46
>>_pdp_+Uc
While I agree with your conclusion

> While this analysis might be completely off, the simple fact that I could get even this information without much efforts is mind-boggling. With better setup it might be able to get more.

This can essentially be rephrased as "I don't know if what the LLM said is true or not but the fact it may or may not be correct is amazing!"

◧◩◪
3. _pdp_+sk[view] [source] 2025-12-03 17:30:18
>>intern+Sh
I don't know what the LLM said is true for sure but based on my experience in the field sounds plausible. The only way to know is to verify it.

Btw, LLMs are already used in vulnerability discovery and exploit development.

[go to top]