Status: closed-fixed Group: v1.0_(example) Created: Tue Sep 09, 2014 07:46 PM UTC by juliusfriedman Last Updated: Wed Sep 10, 2014 05:22 AM UTC Owner: nobody
FYI -- the issue was not in the image decoder itself. Rather, it was that the test file had an excessively long Identifier string in one of the JFIF marker segments. The code has now increased the bounds and properly limits them as required.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the example file to test.
This issue has been fixed in JPEGsnoop version v1.7.1
Awesome, where is the latest version?
Was the fix in the decoder?
On Wed, Sep 10, 2014 at 1:22 AM, Calvin Hass calvinhass@users.sf.net
wrote:
Related
Bugs:
#21Hi Julius!
The fixed version (v1.7.1) will be posted at http://www.impulseadventure.com/photo/jpeg-snoop.html as soon as I have completed testing of other changes. I hope to have it released within a week.
FYI -- the issue was not in the image decoder itself. Rather, it was that the test file had an excessively long Identifier string in one of the JFIF marker segments. The code has now increased the bounds and properly limits them as required.