Often Misused: Authentication: this phrase was inherited from 7PK and used in CWE-247 in Draft 8 and earlier. If only the name is used, it could be interpreted as a very general category that covers anything related to authentication. Closer examination of the description, however, makes it clear that this is a language-specific, OS-specific, low-level variant related to reliance on the getlogin() function.
Mobile Code: Object Hijack: this phrase was inherited from 7PK and used in CWE-491 in Draft 8 and earlier. However, it is attack oriented, and it does not specify the nature of the weakness that allows this attack to occur. In a mapping task, this allows room for multiple interpretations and increases the chance of mapping errors. At least, it forces the reader to perform more research in order to figure out what is being discussed.
Memory Locking: this phrase was used in CWE-591 in Draft 8 and earlier. It is not weakness-focused; it is about a behavior without any specification of what is wrong with the behavior. So it has multiple interpretations, such as:
this could be a category listing all weaknesses that are related to memory locking