New issue
Advanced search Search tips

Issue 875712 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Aug 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Bad-cast to blink::MediaKeySystemConfiguration from invalid vptr in bool WTF::TraceInCollectionTrait<

Project Member Reported by ClusterFuzz, Aug 20

Issue description

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x000000000000
Crash State:
  Bad-cast to blink::MediaKeySystemConfiguration from invalid vptr
  bool WTF::TraceInCollectionTrait<
  blink::ThreadHeap::AdvanceMarking
  
Sanitizer: cfi (CFI)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=582157:582184

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Aug 20

Components: Blink>MemoryAllocator>GarbageCollection
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 sheriffbot@chromium.org, Aug 20

Labels: Target-70 M-70
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 20

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 4 by sheriffbot@chromium.org, Aug 20

Labels: Pri-1
Owner: haraken@chromium.org
Status: Assigned (was: Untriaged)
haraken: Can you take a look at this issue? (And reassign if appropriate?) Thanks.
Cc: haraken@chromium.org mlippautz@chromium.org
Owner: keishi@chromium.org
keishi: Would you mind taking a look at this?

Project Member

Comment 7 by ClusterFuzz, Aug 21

ClusterFuzz has detected this issue as fixed in range 584414:584419.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x000000000000
Crash State:
  Bad-cast to blink::MediaKeySystemConfiguration from invalid vptr
  bool WTF::TraceInCollectionTrait<
  blink::ThreadHeap::AdvanceMarking
  
Sanitizer: cfi (CFI)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=582157:582184
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=584414:584419

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

See https://github.com/google/clusterfuzz-tools 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 8 by ClusterFuzz, Aug 21

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Is this really fixed or just not happening anymore?
Project Member

Comment 10 by sheriffbot@chromium.org, Aug 21

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -ReleaseBlock-Stable
Project Member

Comment 12 by sheriffbot@chromium.org, Nov 27

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