summaryrefslogtreecommitdiffstats
path: root/test/twriteorder.c
diff options
context:
space:
mode:
authorDana Robinson <43805+derobins@users.noreply.github.com>2023-08-02 20:59:26 (GMT)
committerGitHub <noreply@github.com>2023-08-02 20:59:26 (GMT)
commit11e28fe8b84586eb6d99339f45ff3e502e2c5b60 (patch)
treeb17c281c30e1946d6d062551f07a6b4bc196d781 /test/twriteorder.c
parentf5c3963c18ef148622d620691dc9d202aa0b95ed (diff)
downloadhdf5-11e28fe8b84586eb6d99339f45ff3e502e2c5b60.zip
hdf5-11e28fe8b84586eb6d99339f45ff3e502e2c5b60.tar.gz
hdf5-11e28fe8b84586eb6d99339f45ff3e502e2c5b60.tar.bz2
Fix CVE-2018-11202 (#3330)
A malformed file could result in chunk index memory leaks. Under most conditions (i.e., when the --enable-using-memchecker option is NOT used), this would result in a small memory leak and and infinite loop and abort when shutting down the library. The infinite loop would be due to the "free list" package not being able to clear its resources so the library couldn't shut down. When the "using a memory checker" option is used, the free lists are disabled so there is just a memory leak with no abort on library shutdown. The chunk index resources are now correctly cleaned up when reading misparsed files and valgrind confirms no memory leaks.
Diffstat (limited to 'test/twriteorder.c')
0 files changed, 0 insertions, 0 deletions