OpenJPEG: Heap memory corruption leading to invalid free
tcd.cin OpenJPEG 1.3 through 1.5 allows remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code via crafted tile information in a
TIFFimage, which causes insufficient memory to be allocated and leads to an "invalid free".
What are the security implications of the invalid free? How might it be abused or exploited in a security context?
My interest in information security eventually led to an interest in computer science in general, not the other way around: always being less interested in cause than effect.
I recently began trying my hand at writing C code. It's going alright, but still amateur at best. Many of the lower level programming concepts (e.g. heap, memory management, etc.) continue to elude me to a certain extent.
I'm not particularly interested in the specific example provided above. It's just the most recent example (although patched long ago) to inadvertently come across my desk. Anyway, it's a term I'm all too familiar with, from reading and writing reports, yet I have no more than a vague or abstract understanding of what it really implies. Despite the frequency of occurrence, it seems considerably neglected in the common literature. The reports for the CVE above mention remote arbitrary code execution, but it seems to be in addition to the invalid free – the relationship is unclear.