Use After Free (UAF) Vulnerabilities: Explain it Like I’m 5
With the latest high severity vulnerability in Chrome (CVE-2023-5472), use-after-free vulnerabilities have made the news again, and not everyone understands exactly what it means. Use-after-free (UAF) vulnerabilities are related to errors in memory storage, specifically dynamic memory known as the heap. Unlike the stack, which functions almost like a stack of plates (hence the name), where the latest added plate is also the first to be removed; the heap is designed for much larger amounts of data. This heap can be of any size based on what the programmer sets it to.
The solution to these from the application developer’s standpoint is to always ensure that pointers are reset or updated after an action, and must take into account other pointer variables that point to the same location. There are plenty of tools that do this, so that you don’t have to dig through the code by hand. For the user, it highlights the need to always keep your software up to date and to avoid running suspicious programs, as most exploits can be delivered via fake updates or email attachments. To see your exposure if a zero-day where to occur, schedule a demo to see Glassportal in action: demo@glassportal.io