Bloodhound 4.1

With the latest release of Bloodhound 4.1 there is a minor bug where nodes that do not have the highvalue attribute set to true do not end up with the attribute at all.
This causes an issue with GoodHound as it uses this parameter to ascertain paths from non-highvalue nodes to highvalue nodes.

The Patch

When running GoodHound on a set of data that has been gathered using SharpHound 4.1 add the parameter --patch41:

goodhound -p "neo4jpassword" --patch41

This goes through the neo4j database and assigned the highvalue attribute to false anywhere that it isn't already set to true.