Fix null pointer dereference in ResolveAddress#252
Open
hirorogo wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Apr 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ResolveAddressinsrc/sofa/pbrpc/rpc_endpoint.ccunconditionally dereferences theRpcEndpoint* endpointparameter without validating it against NULL. In the 3-argument overload, ifendpointis NULL and DNS resolution succeeds, the write*endpoint = it->endpoint()at line 40 causes a segmentation fault.The 2-argument overload delegates to the 3-argument version, so it is equally affected.
Fix
Add an early
if (!endpoint) return false;guard at the top of bothResolveAddressoverloads, before any dereference occurs. This is a minimal, defensive change that returnsfalse(indicating failure) rather than crashing.PoC
Result:
How it was found
This bug was identified during a SPECA security audit (bug ID: PROP-N1-npd-003).