From github: https://github.com/webcompat/web-bugs/issues/119877.

<!-- @browser: Firefox 112.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/119877 -->

URL: https://1login.wp.pl/zaloguj/2fa/webauthn?login_challenge=Cj0KJDEwYTg2ODIyOTJlYzZlNzM2Y2ZmOWEwYmZkY2Q1Zjc1YWFkMxCyiOugBhoPCglwb2N6dGFfbmgSAnYxEiDWL58hzX-QUfFvyZrIhzf7zlU3tg3wQkCMsRApZSlVQw&challengeId=b473ffd8bc0d4b19b47fb1dc170fc1f4&supportedChannels=WEBAUTHN&supportedChannels=ONETIME

Browser / Version: Firefox 112.0
Operating System: Windows 7
Tested Another Browser: Yes Chrome

Problem type: Something else
Description: problem with using Yubikey
Steps to Reproduce:
When i am trying to log in to my email account using yubikey, after inserting security key to usb port i recive info "something wrong happend, try again", if i tuch button on Yubikey, firefox is shutting down, in firefox v111 i don't have this problem
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2023/3/c16dc1ff-f5b7-4436-b780-c38dd4c73ff3.jpeg">
</details>

<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20230321175953</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

View console log messages

From webcompat.com with ❤️

Change performed by the Move to Bugzilla add-on.

The issue was first reported on Github, via webcompat.com. If the Product and Component are not correct, please feel free to move the issue accordingly.

I was able to reproduce a crash on Firefox 113, but not on 112, in a Windows 7 virtual machine. The attached patch adds a defensive null check to avoid the crash, but it doesn't address the root problem.

It would be helpful if someone could confirm that 112 is affected and find a sequence of operations that reproduces the crash on https://webauthn.io or https://webauthn.bin.coffee.

I finally was able to reproduce this in 112. It will need a different patch. Marking this as leave-open for the follow-up.

https://hg.mozilla.org/mozilla-central/rev/027909737bda

This was fixed in 113 by Bug 1823494. The code is disabled in 112.