BF Specification of CVE-2013-4934 Wireshark v1.8.x before v1.8.9 and v1.10.x before v1.10.1 (trace from SARD-148883)
-0.png)
Missing direct initialization of the 'netmon->frame_table' pointer to NULL leads to a wild pointer, which, when used for explicit deallocation of its object on the heap leads to a Double Free. If exploited, this can lead to denial of service – application crash.
wireshark-1.8.0/wiretap/netmon.c#L
264-#L268
wireshark-1.8.0/wiretap/netmon.c#L905-#L914
vendor:product: wireshark:wireshark:1.8.0 |
| Class | Definition |
| MAD | Memory Addressing (MAD) class – The pointer to an object is initialized, repositioned, or reassigned to an improper memory address. |
| MMN | Memory Management (MMN) class – An object is allocated, deallocated, or resized improperly. |
| Operation | Definition |
| Initialize Pointer | Initialize Pointer operation – Change the undefined data value of a pointer to a meaningful object address; and position the pointer at the start of the object. |
| Deallocate | Deallocate operation – Release the allocated memory of an object. |
| Cause/Consequence | Definition |
| Code Bug | Code Bug type – Defect in the implementation of the operation – proper operands over an improper operation. A first cause for the chain of weaknesses underlying a software security vulnerability. Must be fixed to resolve the vulnerability. |
| Missing Code | Missing Code bug - The operation is entirely absent. |
| Address Error/Fault | Address Fault/Error type – The object address in use is wrong. |
| Wild Pointer | Wild Pointer fault/error – Holds an arbitrary address, because it has not been initialized or an erroneous allocation routine is used. |
| Memory Corruption/Disclosure Final Error | Memory Corruption/Disclosure exploitable error type – An exploitable or undefined system behavior caused by memory addressing, allocation, use, and deallocation bugs. |
| Double Deallocate | Double Deallocate exploitable error – An attempt to deallocate a deallocated (freed) object or via an uninitialized pointer. |
| Operation Attribute | Definition |
| Mechanism | Mechanism operation attribute type – Shows how the buggy/faulty operation code is performed. |
| Direct | Direct operation attribute – The operation is on a particular object element. |
| Explicit | Explicit operation attribute – The operation is via a function/method call. |
| Source Code | Source Code operation attribute type – Shows where the operation with the bug or a faulty operand is in the program – in what kind of software. |
| Codebase | Codebase operation attribute – The operation is in the programmer's code - in the application itself. |
| Execution Space | Execution Space operation attribute type – Shows where the buggy/faulty operation code is running or with what privilege level. |
| Userland | Userland operation attribute – The bugged code runs in an environment with privilege levels, but in unprivileged mode (e.g., ring 3 in x86 architecture). |
| Operand Attribute | Definition |
| Address State | Address State operand attribute type - State operand attribute type – Shows where the address is in the memory layout. |
| Heap | Heap operand attribute – The object is a dynamically allocated data structure (e.g., via malloc() and new). |
| Size Kind | Size Kind operand attribute type – Shows what the limit for traversal of the object is. |
| Used | Used operand attribute – A supplied size for an object. |