In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the NBAP dissector could crash. This was addressed in epan/dissectors/asn1/nbap/nbap.cnf by ensuring DCH ID initialization.
Weakness
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Wireshark |
Wireshark |
2.2.0 (including) |
2.2.12 (including) |
| Wireshark |
Wireshark |
2.4.0 (including) |
2.4.4 (including) |
| Wireshark |
Ubuntu |
artful |
* |
| Wireshark |
Ubuntu |
bionic |
* |
| Wireshark |
Ubuntu |
trusty |
* |
| Wireshark |
Ubuntu |
upstream |
* |
| Wireshark |
Ubuntu |
xenial |
* |
Potential Mitigations
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable’s type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.
References