New issue
Advanced search Search tips

Issue 869713 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 1
Cc:
capn@chromium.org
sugoi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Bad-cast to llvm::cl::Option from llvm::cl::opt<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, false, llvm::cl::parser<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > in llvm::cl::applicator<llvm::cl::FormattingFlags>::opt

Project Member Reported by ClusterFuzz, Aug 1 
Detailed report: https://clusterfuzz.com/testcase?key=5029454632714240

Fuzzer: libFuzzer_gpu_swiftshader_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x7ff7ebdb0a28
Crash State:
  Bad-cast to llvm::cl::Option from llvm::cl::opt<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, false, llvm::cl::parser<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >
  llvm::cl::applicator<llvm::cl::FormattingFlags>::opt
  void llvm::cl::apply<llvm::cl::opt<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, false, llvm::cl::parser<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >, llvm::cl::FormattingFlags, llvm::cl::desc, llvm::cl::initializer<char
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=579136:579142

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Aug 1

Components: Internals>GPU>SwiftShader
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.

Comment 2 by sugoi@chromium.org, Aug 1

Cc: capn@chromium.org
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 1

Labels: M-69 Target-69
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 1

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, Aug 1

Labels: Pri-1
Project Member

Comment 7 by ClusterFuzz, Aug 8

Labels: Needs-Feedback
ClusterFuzz testcase 5029454632714240 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

Comment 8 by infe...@chromium.org, Sep 28

Labels: ClusterFuzz-Ignore
Project Member

Comment 9 by sheriffbot@chromium.org, Nov 8

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

Comment 10 by capn@chromium.org, Nov 26 

Issue 908362 has been merged into this issue.

Comment 11 by sugoi@chromium.org, Dec 14 

Issue 914600 has been merged into this issue.
►

Sign in to add a comment