News for hackers. Stuff that matters.
Re:Windows TCP/IP Remote Code Execution Vulnerability by mylastattempt on Wednesday August 14, 2024 @06:58AM (#41244691)
The CVE has been discovered by a security researcher/firm, rather than being found in the wild. Without technical details or a PoC being publiclya available, I doubt this will amount to more than just another starting point for someone to developer a new exploit. In a year or so it might show up in your Metasploit bundle.
Re:Windows TCP/IP Remote Code Execution Vulnerability by jakeogh on Wednesday August 14, 2024 @07:04AM (#41244730)
Its a odd to take any assertion that "it wasn't seen in the wild" as if in the opposing frame(s) it wasn't "our best technique for over a decade".

Like any valuable secret, the incentives are in the other direction on both sides.

Re:Windows TCP/IP Remote Code Execution Vulnerability by sidewndr46 on Wednesday August 14, 2024 @08:38AM (#41245374)
I don't think that is a realistic conclusion. If one group found it, we can assume that there exists at least one other group that is capable of finding. It therefore is not unrealistic to believe this has seen limited exploitation by sufficiently motivated actors.
Re:Windows TCP/IP Remote Code Execution Vulnerability by acidictadpole on Wednesday August 14, 2024 @11:00AM (#41246897)
> The CVE has been discovered by a security researcher/firm, rather than being found in the wild.

The researcher/firm was the one that disclosed it, but I don't feel like you could conclusively say that the exploit isn't in the wild.

Re:Windows TCP/IP Remote Code Execution Vulnerability by fulafel on Friday August 16, 2024 @02:17AM (#41263619)
Yes, it's sometimes hard to keep in mind that vulnerabilities don't just materialze into existence when they're first publicized. It's a differnt picture, everyone is vulnerable all the time.