This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Using the wrong operator"
From OWASP
Deleted user (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | |||
{{Template:SecureSoftware}} | {{Template:SecureSoftware}} | ||
| Line 57: | Line 56: | ||
Not available. | Not available. | ||
| − | |||
[[Category:Vulnerability]] | [[Category:Vulnerability]] | ||
Revision as of 04:04, 28 May 2006
Overview
This is a common error given when an operator is used which does not make sense for the context appears.
Consequences
Unspecified.
Exposure period
- Pre-design through Build: The use of tools to detect this problem is recommended.
- Implementation: Many logic errors can lead to this condition. It can be exacerbated by lack, of or misuse, of mitigating technologies.
Platform
- Languages: Any
- Operating platforms: Any
Required resources
Any
Severity
Medium
Likelihood of exploit
Low
Avoidance and mitigation
- Pre-design through Build: Most static analysis programs should be able to catch these errors.
- Implementation: Save an index variable. This is the recommended solution. Rather than subtract pointers from one another, use an index variable of the same size as the pointers in question. Use this variable "walk" from one pointer to the other and calculate the difference. Always sanity check this number.
Discussion
These types of bugs generally are the result of a typo. Although most of them can easily be found when testing of the program, it is important that one correct these problems, since they almost certainly will break the code.
Examples
In C:
char foo; foo=a+c;
Related problems
Not available.
