src/bigtiffimage.cpp is longer in the code base however, let's retain this test as support for BigTiff will be developed and the malicious test file may stress the bigtiff parser. Regression test for the bug described in: https://github.com/Exiv2/exiv2/issues/712 A mal
| 2 | |
| 3 | |
| 4 | class BigTiffImageRecursionStackExhaustion( |
| 5 | metaclass=system_tests.CaseMeta): |
| 6 | """ |
| 7 | src/bigtiffimage.cpp is longer in the code base |
| 8 | however, let's retain this test as support for BigTiff will |
| 9 | be developed and the malicious test file may stress the bigtiff parser. |
| 10 | |
| 11 | Regression test for the bug described in: |
| 12 | https://github.com/Exiv2/exiv2/issues/712 |
| 13 | |
| 14 | A malicious input file can cause BigTiffImage::printIFD() to |
| 15 | recurse arbitrarily deep, causing a crash due to stack exhaustion. |
| 16 | |
| 17 | The bug only existed in the -pR mode, which is now only enabled |
| 18 | in debug builds. |
| 19 | """ |
| 20 | url = "https://github.com/Exiv2/exiv2/issues/790" |
| 21 | |
| 22 | filename = system_tests.path( |
| 23 | "$data_path/issue_712_poc.tif" |
| 24 | ) |
| 25 | commands = ["$exiv2 -b -u -k pr $filename"] |
| 26 | stdout = [""] |
| 27 | stderr = [ |
| 28 | """$exiv2_exception_message """ + filename + """: |
| 29 | $filename: $kerFileContainsUnknownImageType |
| 30 | """] |
| 31 | retval = [1] |
nothing calls this directly
no outgoing calls
no test coverage detected