New issue
Advanced search Search tips

Issue 843072 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 843100
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security

Blocking:
issue 62400



Sign in to add a comment

Crash in CFX_BidiLine::Position

Project Member Reported by ClusterFuzz, May 15 2018

Issue description

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

Fuzzer: libFuzzer_pdf_bidi_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: UNKNOWN WRITE
Crash Address: 0x7fa6438762b6
Crash State:
  CFX_BidiLine::Position
  CFX_RTFBreak::EndBreak_BidiLine
  CFX_RTFBreak::EndBreak
  
Sanitizer: memory (MSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=558305:558325

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5841368921145344

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 15 2018

Components: Internals>Plugins>PDF
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, May 15 2018

Cc: dsinclair@chromium.org jam@chromium.org brucedaw...@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 3 by sheriffbot@chromium.org, May 15 2018

Labels: M-68
Project Member

Comment 4 by sheriffbot@chromium.org, May 15 2018

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

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Comment 5 by sheriffbot@chromium.org, May 15 2018

Labels: Pri-1
Owner: dsinclair@chromium.org
Status: Assigned (was: Untriaged)
Blocking: 62400
Labels: -Security_Impact-Head -ReleaseBlock-Stable Security_Impact-None
XFA only.
Mergedinto: 843100
Status: Duplicate (was: Assigned)
Project Member

Comment 9 by ClusterFuzz, May 17 2018

ClusterFuzz has detected this issue as fixed in range 559098:559117.

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

Fuzzer: libFuzzer_pdf_bidi_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: UNKNOWN WRITE
Crash Address: 0x7fa6438762b6
Crash State:
  CFX_BidiLine::Position
  CFX_RTFBreak::EndBreak_BidiLine
  CFX_RTFBreak::EndBreak
  
Sanitizer: memory (MSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=558305:558325
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=559098:559117

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5841368921145344

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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 10 by sheriffbot@chromium.org, Aug 22

Labels: -Restrict-View-SecurityTeam 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