albroland
Joined 7 years ago
Joined 7 years ago
Like yes there is a heap OOB issue in an incredibly old file format, but without already having arguably compromised access to a machine, exploiting it for RCE seems impossible?
- moot was fundraising for his VC backed startup during the years the emails are in, and he was likely connected via mutuals in USV or other firms. These meetings were clearly around him trying to solicit investment in his canv.as project.
- /pol/ was /new/ being returned; the ethos of the board had already existed for a long time and the decision to undo the deletion of /new/ was entirely unsurprising for denizens at the time, and was consistent with a concerted push moot was making for more transparency in the enforcement of rules on the site and fairness towards users who followed the rules. /pol/ didn't start a culture war at this time any more than /new/ had previously - it just existed as a relatively content-unmoderated platform for people to discuss earnestly what would get them banned elsewhere.
This is happening across a lot of web verticals that previously relied on excellent SEO ranking and click through performance to drive ad revenue/conversions/sales. I have direct knowledge of some fairly catastrophic metrics coming out of knowledge base businesses; it wouldn't surprise me in the slightest that something like Tailwind is suffering a similar fate.
How many tanks can you deploy? IFVs? Artillery? How much ammunition can you supply? How many fighters are in service and mission ready? Bombers? Tanker aircraft? Transport? Helicopters? How many battalions (of any type) can be formed/deployed?
Repeat the same exercise in the context of a navy.
https://www.statista.com/statistics/584035/defense-expenditu... https://www.statista.com/statistics/1294391/nato-tank-streng... https://www.statista.com/statistics/1293688/nato-aircraft-st...
Dushanbe I agree with you, but simply because I found Tajikistan rather boring and desolate but in an unimpressive way.
YMMV.
I'm happy to be shown what I'm missing but this seems like a memory corruption bug, not RCE, and if it was feasible w/o the custom buffer then why not provide that as the example? In the real world, a ffmpeg invocation would use the default buffer handler that will use padding/alignment/etc that makes the heap even less predictable, and incredibly unlikely to have a function pointer exactly following the frame buffer that will deterministically be invoked by a process placing it there?
It seems very far fetched.