Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(parser): safer get_error_reason #697

Merged
merged 2 commits into from
Apr 7, 2021
Merged

fix(parser): safer get_error_reason #697

merged 2 commits into from
Apr 7, 2021

Conversation

dnlup
Copy link
Contributor

@dnlup dnlup commented Apr 7, 2021

Check that the returned pointer is valid befire retrieving the error
message.

Fixes #684

Check that the returned pointer is valid befire retrieving the error
message.
@dnlup dnlup requested review from ronag and mcollina April 7, 2021 14:57
lib/client.js Outdated Show resolved Hide resolved
Check for truthy instead of zero in `get_error_reason`

Co-authored-by: Robert Nagy <[email protected]>
@ronag ronag merged commit a15dc41 into main Apr 7, 2021
@dnlup dnlup deleted the parser_error_reason branch April 7, 2021 15:59
crysmags pushed a commit to crysmags/undici that referenced this pull request Feb 27, 2024
* fix(parser): safer get_error_reason

Check that the returned pointer is valid befire retrieving the error
message.

* fix(parser): update pointer check in execute

Check for truthy instead of zero in `get_error_reason`

Co-authored-by: Robert Nagy <[email protected]>

Co-authored-by: Robert Nagy <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

parser error reason reading is not safe
2 participants