5 ms·
> [$16000][1515930] High CVE-2024-0517: Out of bounds write in V8. Reported by Toan (suto) Pham of Qrious Secure on 2024-01-06 > [$1000][1507412] High CVE-2024
by frankjr 3y ago
> [$16000][1515930] High CVE-2024-0517: Out of bounds write in V8. Reported by Toan (suto) Pham of Qrious Secure on 2024-01-06
> [$1000][1507412] High CVE-2024-0518: Type Confusion in V8. Reported by Ganjiang Zhou(@refrain_areu) of ChaMd5-H1 team on 2023-12-03
> [$TBD][1517354] High CVE-2024-0519: Out of bounds memory access in V8. Reported by Anonymous on 2024-01-11
Damn. Google should really hire HN's C++ experts because they would never make errors like this.
- kramerger 3y ago[flagged]
- ajross 3y agoTo take the point more seriously than you intended it: this is (apparently) a bug in a code generator. The C++ itself wasn't unsafe and didn't crash, it emitted binary code that did. A Rust/Python/whatever JIT could trivially have the same bug. Commenters aren't suggesting Rust because it's not an area where implementation language is able to provide safety.
- deleted 3y ago[deleted]
- zeusk 3y agoIronically they need all this complexity to make an interpreted script run faster.
- deleted 3y ago[deleted]
- fwsgonzo 3y agoI wonder if any of these are avoided by disabling JIT, which I have done. And also, just how much of the codebase is JIT related? I also don't think C++ is always the problem. This is a complex language run-time, and there's all sorts of issues that can be language and language run-time related, regardless of it being written in Rust or C++, that manifest as out-of-bounds errors. I couldn't find any information about work-arounds.