New issue
Advanced search Search tips

Issue 711260 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security

Blocking:
issue 62400



Sign in to add a comment

Use-of-uninitialized-value in CFX_SAXReader::ParseChar

Project Member Reported by ClusterFuzz, Apr 13 2017

Issue description

Project Member

Comment 1 by sheriffbot@chromium.org, Apr 13 2017

Labels: M-59
Project Member

Comment 2 by sheriffbot@chromium.org, Apr 13 2017

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 3 by sheriffbot@chromium.org, Apr 13 2017

Labels: Pri-1
Cc: tsepez@chromium.org
Components: Internals>Plugins>PDF
There's nothing obvious to me in the regression range, though I don't know what pdfium depends on (webkit?)

Tom -- Can you take a look?
Project Member

Comment 5 by ClusterFuzz, Apr 14 2017

ClusterFuzz has detected this issue as fixed in range 464315:464333.

Detailed report: https://clusterfuzz.com/testcase?key=5744815947120640

Fuzzer: libfuzzer_pdf_cfx_saxreader_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  CFX_SAXReader::ParseChar
  CFX_SAXReader::ContinueParse
  _start
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=464294:464315
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=464315:464333

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95DHX2NxshCwrdwEC-N3BfBEXS-gEMqhdp6QAOOJmkQ0pot7W8GX_pE-71mak_ys9XaolqtEShQQ0p2KNdhPtZm4cjRVYGDsct7-rVf2mgFfRReDILyjRIQonCNVnDNTMi4FUGM-3HRjyPUwwOtu8RGpn0qCi_jniuIH9F4tCMh5PhE7SKwaPBuJmujhOiz4w_YLZO5k4qHI2HV7a8h0yyjS9sV346AnrDpnJKccOhqrxi_SuUx45G8ezEZlZ9PoTEmCB21GajOpIMRVxPxLw5Y5n2i92MdEX6JkSsnb7pmDPMbf9GNDcMCpqGALjanMdOnLX0MD6iIWV3eMSi3cUrEsElDofzlDJabjPnzx9dQpvkN2AI?testcase_id=5744815947120640


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 6 by ClusterFuzz, Apr 14 2017

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

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

Comment 7 by sheriffbot@chromium.org, Apr 14 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -ReleaseBlock-Beta
Blocking: 62400
Labels: -Security_Impact-Head -M-59 Security_Impact-None ClusterFuzz-Wrong
Status: Available (was: Verified)
We should verify if this was fixed.

This is XFA code, so not enabled in ToT. Removing the Security_Impact-Head.
Status: Fixed (was: Available)
https://pdfium-review.googlesource.com/4230 should have taken care of this.
Project Member

Comment 11 by sheriffbot@chromium.org, Jul 28 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
Labels: -ClusterFuzz-Wrong
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.

Sign in to add a comment