You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the outbound peers on incompatible chains may use up outbound connection slots (the ProcessMessage() function in src/main.cpp). If the block header is valid, but the block is known to be invalid, and the peer announces the same block as being on its active chain, the peer should be disconnected.
A possible solution is to check whether the first invalid header in mapBlockIndex is at the end, if not, disconnect the peer (after line 5758 in src/main.cpp).
I'm using this to respond for all the issues you've opened. First of all thank you for reporting them. We're currently focused on a major delivery of zend_oo and there is no further release planned from this repository. We will address all of the issues on the zend_oo repository in the coming weeks.
This is a security vulnerability.
Currently, the outbound peers on incompatible chains may use up outbound connection slots (the
ProcessMessage()
function insrc/main.cpp
). If the block header is valid, but the block is known to be invalid, and the peer announces the same block as being on its active chain, the peer should be disconnected.A possible solution is to check whether the first invalid header in
mapBlockIndex
is at the end, if not, disconnect the peer (after line 5758 insrc/main.cpp
).Similar fix from Bitcoin: bitcoin/bitcoin@37886d5.
Reported by
6004ed5feaa31ae9df36b5dbc60f0fa53255a5fb734334082c6d202405fc738c
.The text was updated successfully, but these errors were encountered: