CVE-2022-29693

Unicorn Engine v2.0.0-rc7 and below was discovered to contain a memory leak via the function uc_close at /my/unicorn/uc.c.

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

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)

Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
For example, glibc in Linux provides protection against free of invalid pointers.
When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2022-29693
CWE	https://cwe.mitre.org/data/definitions/401.html

Missing Release of Memory after Effective Lifetime