Chrome/ChromeOS uses vulnerable version of libpng
Reported by
steffz...@gmail.com,
Jan 3 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9000.29.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.28 Safari/537.36 Platform: 9000.29.0 (Official Build) beta-channel edgar Steps to reproduce the problem: 1. visit chrome://os-credits/ and note libpng version 1.6.25 2. read vulnerability report https://www.cert-bund.de/advisoryshort/CB-K17-0003 3. notice that version prior to 1.6.27 are vulnerable What is the expected behavior? Chrome should use software without known and corrected vulnerabilities. What went wrong? See https://www.cert-bund.de/advisoryshort/CB-K17-0003 Did this work before? N/A Chrome version: 56.0.2924.28 Channel: beta OS Version: 9000.29.0 Flash Version:
,
Jan 3 2017
We don't consider NULL dereferences to be a security bug because they are not exploitable (see http://dev.chromium.org/Home/chromium-security/reporting-security-bugs, "Signs A Crash Is Not A Security Bug"). That said, what elawrence@ writes at #1 is relevant and we should probably update libpng.
,
Feb 9 2017
Sure, we should absolutely keep our copy of libpng up to date. However, I can verify that we do not do the sequence of operations described in #1, so we are not vulnerable. Closing this bug. |
|||
►
Sign in to add a comment |
|||
Comment 1 by elawrence@chromium.org
, Jan 3 2017