| CWE-705 |
The software does not properly return control flow to the proper location after it has completed a task or detected an unusual condition. |
| CWE-706 |
The software uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. |
| CWE-707 |
The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component. |
| CWE-708 |
The software assigns an owner to a resource, but the owner is outside of the intended control sphere. |
| CWE-71 |
This entry has been deprecated as it represents a specific observed example of a UNIX Hard Link weakness type rather than its own individual weakness type. Please refer to CWE-62. |
| CWE-710 |
The software does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities. |
| CWE-72 |
The software does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system. |
| CWE-73 |
The software allows user input to control or influence paths or file names that are used in filesystem operations. |
| CWE-732 |
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. |
| CWE-733 |
The developer builds a security-critical protection mechanism into the software, but the compiler optimizes the program such that the mechanism is removed or modified. |
