4 ms·
The ACTUAL writeup: https://www.qualys.com/2023/10/03/cve-2023-4911/looney-tunables-local-privilege-escalation-glibc-ld-so.txt https://www.qualys.com/2023/10/03
by fargle 3y ago
The ACTUAL writeup: https://www.qualys.com/2023/10/03/cve-2023-4911/looney-tunables-local-privilege-escalation-glibc-ld-so.txt https://www.qualys.com/2023/10/03/cve-2023-4911/looney-tunab...
- dang 3y agoOk, we've changed to that from https://blog.qualys.com/vulnerabilities-threat-research/2023/10/03/cve-2023-4911-looney-tunables-local-privilege-escalation-in-the-glibcs-ld-so https://blog.qualys.com/vulnerabilities-threat-research/2023... above. Thanks!
- stevekemp 3y agoI guess this now makes it a duplicate of https://news.ycombinator.com/item?id=37754973 https://news.ycombinator.com/item?id=37754973
- dang 3y agoIn principle yes, but we don't count a repost as a dupe unless the earlier thread got significant attention. (This is in the FAQ: https://news.ycombinator.com/newsfaq.html https://news.ycombinator.com/newsfaq.html.) In the case of 37754973 it got a fair number of upvotes but still never made the front page. So I think it's fair not to call the current thread a dupe. I'm sorry I forgot to check if someone had already submitted the better URL. Usually I do check that, and re-up the earlier submission rather than switching the URL on the later one. Edit: but we can at least merge the comments thither so https://news.ycombinator.com/item?id=37754973 https://news.ycombinator.com/item?id=37754973 becomes the canonical post on the topic. I've done that now.