- cross-posted to:
- programming@lemmy.ml
- cross-posted to:
- programming@lemmy.ml
You must log in or # to comment.
This needs to be in cve-rs (I’m too lazy for that tho)
A PR fixing the issue has already been submitted (which surfaced another issue, but it doesn’t concern stable).
People likening this to the issue behind cve-rs (which is blocked on a major rework) are clueless, which happens to be par for the course regarding anything Rust. So no surprises there.
I just find cve-rs hilarious, disregarding if the issue is fixed or not :)
So THIS is why my Rust app kept refusing to compile!
(/jk)
Yes. That, and no other reason 👍
Nah… Its probably due to a common bug found in DNA compilers 😺
Given that this issue has been shared online and is currently getting quite a few visitors, here’s some additional context.
Rust’s type system is intended to prevent memory unsafety. Upholding this promise is something we take very seriously, which is why we’ve been working on things like the next-generation trait solver, the region constraint rework, and more generally Project Zero. It is a large priority of the Types Team to fix all type system unsoundnesses and to work towards there being a solid foundation to minimize the risk of unknown ones.
This bug is a P-high issue and would have been P-critical regardless of whether people encountered it in the wild. The reason that it is “only P-high” is that it’s 11 years old. A bug like this which has not been found during the last 11 years cannot actually be that easy to hit.
Looking at the bug itself, it is also very likely that this unsoundness has not caused memory unsafety by accident. While it looks easy to trigger, to exploit this you need an intentionally malicious Drop implementation.
A bug like this which has not been found during the last 11 years cannot actually be that easy to hit.
Not sure why but I found this completely justified reasoning to be very funny. Getting ahead of the people complaining that it needs fixing NOW by saying, correctly, “it’s not that serious”
I do this at work all the time “this tech has been available to us for the past 20 years and you did nothing with it, now you want it done in a year?”