New issue
Advanced search Search tips

Issue 675954 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 675617
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in fclamp

Project Member Reported by ClusterFuzz, Dec 20 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5752835670278144

Fuzzer: libfuzzer_pdf_codec_icc_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  fclamp
  BilinearInterpFloat
  _LUTevalFloat
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=430492:430537

Minimized Testcase (0.85 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96obCviqfxepPB0XsxIf3YIBSKhgmLUn_7wJMu4fnNhcms2tJIIERHykiBfhBOoXNxcTpGe1aa9s9vrKvlF8uCjFfnlHaBwooW6Btku0HenbaaNl0Nia1j-_vRZTjY2D1AISOFWUO2V1RdOWef6jEzwVBrWpQ?testcase_id=5752835670278144

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Components: Internals>Plugins>PDF
Owner: kcwu@chromium.org
Status: Assigned (was: Untriaged)
kcwu: another fclamp uninitialized value usage for you. :)
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 21 2016

Labels: M-57
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 21 2016

Labels: ReleaseBlock-Beta
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 21 2016

Labels: Pri-1
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 4 2017

kcwu: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by sheriffbot@chromium.org, Jan 18 2017

kcwu: Uh oh! This issue still open and hasn't been updated in the last 28 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by gov...@chromium.org, Jan 23 2017


A friendly reminder that M57 Beta launch is coming soon on February 2nd! Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix and get it merged into the release branch (2987) ASAP so it gets enough baking time in Dev (before Beta promotion). Thank you!

Comment 8 by gov...@chromium.org, Jan 25 2017

[Bulk edit]

A friendly reminder that M57 Beta launch is coming soon on February 2nd (in a week)! Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix and get it merged into the release branch (2987) ASAP so it gets enough baking time in Dev (before Beta promotion). Thank you!
Project Member

Comment 9 by sheriffbot@chromium.org, Jan 26 2017

Labels: -Security_Impact-Head Security_Impact-Beta
Labels: -ReleaseBlock-Beta -Security_Impact-Beta ReleaseBlock-Stable Security_Impact-Stable
A friendly reminder that M57 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

Hi kcwu@ - are you best placed to look at this?  If not please re-assign.

A friendly reminder that M57 Stable is launch is coming VERY soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch (2987) ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!
Cc: wuchengli@chromium.org posciak@chromium.org
The issue is in pdfium? I don't think Kuang-che touched that code before. Kuang-che?

Comment 16 by kcwu@chromium.org, Feb 22 2017

Cc: kcwu@chromium.org
Owner: dsinclair@chromium.org
I don't have free time to help. Reassigned.

URGENT - PTAL ASAP.

We're getting VERY close to M57 Stable promotion. And 
this issue is marked as M57 stable release blocker. Pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion).

Know that this issue shouldn't block the release?  Remove the ReleaseBlock-Stable label or move to M58.

Thank you.
Cc: -posciak@chromium.org -wuchengli@chromium.org
Cc: dsinclair@chromium.org
Owner: npm@chromium.org
npm@ can you please take a look?

Comment 20 by npm@chromium.org, Feb 22 2017

Looks like the fix for  issue 675617  will also fix this, but unable to confirm because for some reason I can't reproduce locally. Will rerun clusterfuzz once the fix has landed.
Project Member

Comment 21 by ClusterFuzz, Feb 23 2017

ClusterFuzz has detected this issue as fixed in range 452161:452203.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5752835670278144

Fuzzer: libfuzzer_pdf_codec_icc_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  fclamp
  BilinearInterpFloat
  _LUTevalFloat
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=430492:430537
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=452161:452203

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94fWRyTWsoj4K_8tQyQ-s1Ej7oh90y-aBLmEaNDthh0mvUmdREMJmKIfPwX5gDCxUJquQhkak4GMqg62peFW85BkguNdwHcOXLZELpy68GEUWNqlt37tNSTa_H3vLWleYpjDD8TL8tybgCwMqOBIBbK4Ww2rhChHrau6qnz1_ZeNllOcSVaHtDLSk64TNn9UMGRernk4lNRM2R9f1USKpZggWjivJSjAEuz81C9VKPOZDG3E8I1jccvP5GKdhRsSOarChuqv3FMFVji3nB2BYGA6lmV9nf5IxvUwDqFViHkJkiUhILu067-GaxG1BV_uFOWAUdCPiV_uFL_SAPYfoel8ssmPSl-Ys-iVALvJTsPQl-HO54?testcase_id=5752835670278144


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 22 by ClusterFuzz, Feb 23 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5752835670278144 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 23 by sheriffbot@chromium.org, Feb 23 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify

Comment 24 by npm@chromium.org, Feb 23 2017

Mergedinto: 675617
Status: Duplicate (was: Verified)
Project Member

Comment 25 by sheriffbot@chromium.org, Jun 2 2017

Labels: -Restrict-View-SecurityNotify allpublic
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment