Skip to content

Fix crash in parseJsxChild found by fuzzing - #53674

Merged
jakebailey merged 1 commit into
microsoft:mainfrom
jakebailey:fix-another-crash
Apr 5, 2023
Merged

Fix crash in parseJsxChild found by fuzzing#53674
jakebailey merged 1 commit into
microsoft:mainfrom
jakebailey:fix-another-crash

Conversation

@jakebailey

Copy link
Copy Markdown
Member

Found this case in fuzzing.

This fix is basically the same as #52450. I didn't change this location because I thought it couldn't be hit, but, I was wrong!

The crash already occurs before 5.0, but the assert moved from one place to another in #52667. So this isn't a 5.0 regression, per se.

@typescript-bot typescript-bot added Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug labels Apr 5, 2023
@jakebailey

Copy link
Copy Markdown
Member Author

@DanielRosenwasser Should this be backported?

@jakebailey

Copy link
Copy Markdown
Member Author

I think the answer is no, for now, but if someone reports this we can grab it. But, it would crash before, so probably not.

@jakebailey jakebailey closed this Apr 5, 2023
@jakebailey jakebailey reopened this Apr 5, 2023
@jakebailey
jakebailey merged commit f243b98 into microsoft:main Apr 5, 2023
@jakebailey
jakebailey deleted the fix-another-crash branch April 5, 2023 20:47
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants