Not really, the issue is that C/C++ is not memory safe, i.e. it allows you to access memory that has already been freed. Consider the following C++ code:

int* wrong() {
  int data  = 10;
  return &data;
}

If you try to use it it looks correct:

int* ptr = wrong();
std::cout << *ptr << std::endl;

That will print 10, but the memory where data was defined has been freed, and is no longer in control of the program. Meaning that if something else allocated that memory they can control what my program does.

Consider that on that example above later in the program we do:

user.access_level = *ptr;

If someone manages to get control of that memory between when we freed it and we used it they can make the access_level of the user be whatever they want.

This is a problem with C/C++ allowing you to access memory that has been freed, which is why C/C++ programmers need to be extra careful.