An issue in Cppcheck 2.12 dev allows a local attacker to execute arbitrary code via the removeContradiction parameter in token.cpp:1934.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Cppcheck | Cppchecksolutions | 2.12.0 (including) | 2.12.0 (including) |
| Cppcheck | Ubuntu | bionic | * |
| Cppcheck | Ubuntu | focal | * |
| Cppcheck | Ubuntu | lunar | * |
| Cppcheck | Ubuntu | mantic | * |
| Cppcheck | Ubuntu | oracular | * |
| Cppcheck | Ubuntu | trusty | * |
| Cppcheck | Ubuntu | trusty/esm | * |
| Cppcheck | Ubuntu | xenial | * |