valgrind errors with unittest IlmImfCtlTest - memory leak - 224 bytes directly lost, 48 bytes indirectly lost about ctl HOT 1 CLOSED

I think this memory leak reported by valgrind in IlmImfCtlTest is actually a bug in ilmbase v2.3. I do not think it is a bug in the CTL codebase.

ilmbase v2.3 is currently available via Ubuntu 20.04 package manager, i.e. sudo apt-get install libilmbase-dev

This page https://packages.ubuntu.com/focal/libilmbase-dev provides the ilmbase v2.3 code that is available via Ubuntu 20.04 package manager, it is identical to the source code within the directory IlmBase available from source https://github.com/AcademySoftwareFoundation/openexr/tree/RB-2.3

Building/installing openexr/ilmbase v2.5 from source https://github.com/AcademySoftwareFoundation/openexr/tree/RB-2.5 on Ubuntu 20.04 first before compiling and running valgrind on /CTL/unittest/IlmImfCtlTest fixes this memory leak, with valgrind reporting no leaks when using openexr/ilmbase v2.5 compiled from source.

The attached Dockerfile.zip contains a Dockerfile that builds openexr/ilmbase v2.5 from source on Ubuntu 20.04 before building CTL

I expect this is the same CVE-2018-18443 CVE-2018-18443 bug as reported in aswf/openexr issue 350 AcademySoftwareFoundation/openexr#350

It looks like aswf/openexr issue 350 AcademySoftwareFoundation/openexr#350 was fixed by aswf/openexr pull request 412 AcademySoftwareFoundation/openexr#412 with commit 5fa930b by @kdt3rd This fix was included in aswf openexr/ilmbase release v2.4.0, but has not been backported to openexr/ilmbase v2.3 or v2.2 that I believe are still widely deployed.

from ctl.