What is a MUTEX?
A mutual exclusion object, or MUTEX, is an object created for use in computer programs. The essential function of MUTEX is to make it possible for a multiple program thread to make use of a single resource. Generally, the functionality of mutual exclusion objects is to allow this use of a single resource by creating an environment where the access to the resource is continually passed back and forth between the various aspects of the program. The process of activating and creating a MUTEX takes place when the computer program application is opened. Essentially, the program will create the MUTEX and relate it to a specific resource that is needed for the efficient function of the open program. As the resources is called forth, the operating system will assign a unique name to the MUTEX and use it to identify the process for as long as the program remains open. Once the MUTEX is activated and named for the session, any other thread of the program that requires this resource can have acce
A mutex is a synchronization object used to prevent more than one process from accessing certain resources at the same time. Multiprocessing operating systems like Windows NT 4.0 allow multiple programs to run at the same time. However, even so, there are certain resources that can only be used by one program at a time. Mutexes are used to help control access to resources like these. What’s the problem with mutexes in Windows NT 4.0? There’s no problem with mutexes in general. However, mutexes, like all objects in Windows NT 4.0, have permissions that regulate how and by whom they can be accessed. The mutex involved in this vulnerability has inappropriate permissions. By design, this mutex should only be accessible by programs with administrator or system privileges; however, in reality, everyone can access it. As a result, an attacker could write a program that waits its turn for the mutex and change its permissions allowing no access. If this happened, no other program could use the
