Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

From 196 not solved, security #352

Closed
bastien-roucaries opened this issue Jan 11, 2017 · 1 comment
Closed

From 196 not solved, security #352

bastien-roucaries opened this issue Jan 11, 2017 · 1 comment

Comments

@bastien-roucaries
Copy link

Three CVEs have been assigned for those issues. AFAICT, the one for the error handling of the fwrite's in ReadGROUP4Image would still be open?

Check return of write function

Debian bug: https://bugs.debian.org/845196
Reference URL: https://security-tracker.debian.org/845196
Upstream commit:

The above fixes may be incomplete, according to the upstream issue. In
addition, the -6 branch seems to have an incomplete fix as well.

Use CVE-2016-10060 for the issue fixed in 933e96f.
Use CVE-2016-10061 for the issue fixed in 4e914bb.

Use CVE-2016-10062 for the fwrite issue in ReadGROUP4Image. This was
specifically noted at the beginning of issues/196, but not fixed in
either of these commits. It is not the same as the fputc issue in
ReadGROUP4Image.

Origin: https://marc.info/?l=oss-security&m=148278818528413&w=2

@mikayla-grace
Copy link

Best practices suggest that an application check the status of each and every system call and we're working on that over time. #196 was classified as a low priority because no reproducible exploit was provided. However, renewed interest in the issue pushes the priority higher. Consequently we intend to provide a patch within the next few days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants