The Node.js project recently had a security vulnerability that affected its Brotli decoder. The bug was a buffer overflow, but the particular way that official Node.js binaries are built for Linux meant that one of the main protections against turning a buffer overflow into remote code execution, address space layout randomization (ASLR) could not be turned on. If ASLR had been enabled, the bug would still be exploitable in theory, but much more difficult to exploit in practice. In response, the GNU C Library (glibc) is considering a new set of tunable settings to allow administrators to forbid programs that do not support ASLR. The new settings, while a welcome hardening measure, may not address the root problem.
Security![[$] Additional hardening for the glibc dynamic linker](/storage/uploads/covers/auto/p210667.svg)
[$] Additional hardening for the glibc dynamic linker
LWN.net0 views
Source:https://lwn.net/Articles/1105134/
PreviousiPhone 18 Pro Max Wins Battery Test Involving 32 SmartphonesNextAmazon's Ring Unveils Flying Drone and Robot To Patrol Homes and Businesses
Related posts
Show HN: Local-first emerging-threat detector for the cybersecurity news stream
0Hacker News Show

Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations
0AWS Compute Blog

Building a GPU workstation for visual effects with Amazon EC2: Part 5 – Security
0AWS Compute Blog
Blind trust: stealing credentials through CSP
0PortSwigger Research
Can green technologies deliver energy security in an unstable world?
0Nature News
Address Poisoning Attacks: One Copy-Paste From Ruin
0dev.to