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

net/rpc/jsonrpc: client nil pointer deference on invalid reply #5006

gopherbot opened this issue Mar 8, 2013 · 4 comments

net/rpc/jsonrpc: client nil pointer deference on invalid reply #5006

gopherbot opened this issue Mar 8, 2013 · 4 comments


Copy link

@gopherbot gopherbot commented Mar 8, 2013

by nos.adrian:

Returning invalid data to the client can result in a nil pointer deference:

Unit test & proposed fix attached.


  1. jsonrpc.patch (1600 bytes)
Copy link

@ianlancetaylor ianlancetaylor commented Mar 8, 2013

Comment 1:

Labels changed: added go1.1maybe.

Copy link

@robpike robpike commented Mar 8, 2013

Comment 2:

Thanks. Fix looks right to me.
You are not on the official Go contributors list. The fix is tiny so I'm happy to make
it myself if you want to avoid the minor bureaucracy that entails, or you can go through
the official channels by following the instructions at
Please advise.

Labels changed: added priority-later, go1.1, removed priority-triage, go1.1maybe.

Status changed to WaitingForReply.

Copy link

@gopherbot gopherbot commented Mar 11, 2013

Comment 3 by nos.adrian:

I think I managed all the steps required. issue #7691045 should be available for review.
Copy link

@rsc rsc commented Mar 12, 2013

Comment 4:

This issue was closed by revision 0d559f7.

Status changed to Fixed.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.