davidben@ /svaldez@ could you please look into this.please feel free to re-assigned back if needed. thanks in advance !

This is being worked on. (This doesn't affect Chrome, only affects the TLS 1.3 code which is yet to be turned on, and requires an attacker to have broken a server's ticket key and forge an invalid ticket. So it's not terribly critical. Still, good to fix.)

 Issue 659418  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 428469:428574.

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

Fuzzer: libfuzzer_boringssl_server_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  fixed_iv_len <= sizeof(aead_ctx->fixed_nonce)
  SSL_AEAD_CTX_new
  tls13_set_traffic_key
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=425081:425196
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=428469:428574

Minimized Testcase (1.70 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94C_uMiHE8tY_muhN-G74mEQ7f-mqxWzzTPILWV8tB5C2eKW_UQ_X1W8sdBEl3gRL3iyMqtSwojDkJK6j2UF6icq7XxpNFU7obZ8XNzNuXu0zTbHcUaJORPJRKOjpIue-GMaIMExR1HTOpe5J5ANqEXqEJkxw?testcase_id=6052858253541376

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.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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