Unicorn Engine v2.0.0-rc7 contains memory leaks caused by an incomplete unicorn engine 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 |
|---|---|---|---|
| Unicorn_engine | Unicorn-engine | * | 2.0.0 (excluding) |
| Unicorn_engine | Unicorn-engine | 2.0.0 (including) | 2.0.0 (including) |
| Unicorn_engine | Unicorn-engine | 2.0.0-rc1 (including) | 2.0.0-rc1 (including) |
| Unicorn_engine | Unicorn-engine | 2.0.0-rc2 (including) | 2.0.0-rc2 (including) |
| Unicorn_engine | Unicorn-engine | 2.0.0-rc3 (including) | 2.0.0-rc3 (including) |
| Unicorn_engine | Unicorn-engine | 2.0.0-rc4 (including) | 2.0.0-rc4 (including) |
| Unicorn_engine | Unicorn-engine | 2.0.0-rc5 (including) | 2.0.0-rc5 (including) |
| Unicorn_engine | Unicorn-engine | 2.0.0-rc6 (including) | 2.0.0-rc6 (including) |
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.