In the DataBuf class in include/exiv2/types.hpp in Exiv2 0.26, an issue exists in the constructor with an initial buffer size. A large size value may lead to a SIGABRT during an attempt at memory allocation. NOTE: some third parties have been unable to reproduce the SIGABRT when using the 4-DataBuf-abort-1 PoC file.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://bugzilla.novell.com/show_bug.cgi?id=1087879 | third party advisory issue tracking |
https://github.com/xiaoqx/pocs/tree/master/exiv2 | third party advisory exploit |
https://security.gentoo.org/glsa/201811-14 | third party advisory vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=1564281 | third party advisory issue tracking |