Parent Class without Virtual Destructor Method

When you delete a child class object through a pointer to its non-virtual parent, the program calls only the parent's destructor. The child class's own destructor is never invoked, leading to a partial destruction known as 'object slicing.' This leaves the child's resources, like dynamically allocated memory or open file handles, uncleaned—a direct path to memory leaks and corrupted program state. From a security perspective, while not a direct vulnerability, this unreliable behavior undermines system stability. An attacker who can trigger code paths that rely on this flawed inheritance chain can cause resource exhaustion, crashes, or unexpected behavior. These conditions can potentially be leveraged to bypass security controls or contribute to a larger exploit chain, making the application less predictable and more difficult to defend.