|
|
| (6 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | {{Template:Vulnerability}}
| + | #REDIRECT [[Doubly_freeing_memory]] |
| − | {{Template:Fortify}}
| |
| − | | |
| − | __TOC__
| |
| − | | |
| − | [[ASDR Table of Contents]] | |
| − | | |
| − | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
| |
| − | | |
| − | | |
| − | [[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
| |
| − | | |
| − | | |
| − | ==Description==
| |
| − | | |
| − | Double free errors occur when free() is called more than once with the same memory address as an argument.
| |
| − | | |
| − | Calling free() twice on the same value can lead to a buffer overflow. When a program calls free() twice with the same argument, the program's memory management data structures become corrupted. This corruption can cause the program to crash or, in some circumstances, cause two later calls to malloc() to return the same pointer. If malloc() returns the same value twice and the program later gives the attacker control over the data that is written into this doubly-allocated memory, the program becomes vulnerable to a buffer overflow attack.
| |
| − | | |
| − | | |
| − | ==Risk Factors==
| |
| − | | |
| − | * Talk about the [[OWASP Risk Rating Methodology|factors]] that make this vulnerability likely or unlikely to actually happen
| |
| − | * Discuss the technical impact of a successful exploit of this vulnerability
| |
| − | * Consider the likely [business impacts] of a successful attack
| |
| − | | |
| − | | |
| − | ==Examples==
| |
| − | | |
| − | The following code shows a simple example of a double free vulnerability.
| |
| − | | |
| − | <pre>
| |
| − | char* ptr = (char*)malloc (SIZE);
| |
| − | ...
| |
| − | if (abrt) {
| |
| − | free(ptr);
| |
| − | }
| |
| − | ...
| |
| − | free(ptr);
| |
| − | </pre>
| |
| − | | |
| − | Double free vulnerabilities have two common (and sometimes overlapping) causes:
| |
| − | | |
| − | * Error conditions and other exceptional circumstances
| |
| − | * Confusion over which part of the program is responsible for freeing the memory
| |
| − | | |
| − | Although some double free vulnerabilities are not much more complicated than the previous example, most are spread out across hundreds of lines of code or even different files. Programmers seem particularly susceptible to freeing global variables more than once.
| |
| − | | |
| − | | |
| − | ==Related [[Attacks]]==
| |
| − | | |
| − | * [[Attack 1]]
| |
| − | * [[Attack 2]]
| |
| − | | |
| − | | |
| − | ==Related [[Vulnerabilities]]==
| |
| − | | |
| − | * [[Vulnerability 1]]
| |
| − | * [[Vulnerabiltiy 2]]
| |
| − | | |
| − | | |
| − | ==Related [[Controls]]==
| |
| − | | |
| − | * [[Control 1]]
| |
| − | * [[Control 2]]
| |
| − | | |
| − | | |
| − | ==Related [[Technical Impacts]]==
| |
| − | | |
| − | * [[Technical Impact 1]]
| |
| − | * [[Technical Impact 2]]
| |
| − | | |
| − | | |
| − | ==References==
| |
| − | TBD
| |
| − | | |
| − | [[Category:FIXME|add links
| |
| − | | |
| − | In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
| |
| − | | |
| − | Availability Vulnerability
| |
| − | | |
| − | Authorization Vulnerability
| |
| − | | |
| − | Authentication Vulnerability
| |
| − | | |
| − | Concurrency Vulnerability
| |
| − | | |
| − | Configuration Vulnerability
| |
| − | | |
| − | Cryptographic Vulnerability
| |
| − | | |
| − | Encoding Vulnerability
| |
| − | | |
| − | Error Handling Vulnerability
| |
| − | | |
| − | Input Validation Vulnerability
| |
| − | | |
| − | Logging and Auditing Vulnerability
| |
| − | | |
| − | Session Management Vulnerability]]
| |
| − | | |
| − | __NOTOC__
| |
| − | | |
| − | | |
| − | [[Category:OWASP ASDR Project]]
| |
| − | [[Category:Code Quality Vulnerability]]
| |
| − | [[Category:Implementation]]
| |
| − | [[Category:Code Snippet]]
| |
| − | [Category:Vulnerability]]
| |
