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
Describe the bug
The BloodHound Web UI is unable to gracefully handle/display duplicate relationships to the same nodes. See the attached Neo4j screenshot below.
To Reproduce
Easy steps to reproduce the behavior:
Pick a node, let's say a User Account (JEFF) and a Computer (WK1)
Use Neo4j to manually establish multiple relationships (ex. HasSession) from Jeff to WK1 two times over:
Execute the following neo4j query twice: MATCH (u:User {name: "[email protected]"}) MATCH (c:Computer {name: "WK1.DOMAIN.COM"}) CREATE (c)-[:HasSession]->(u)
Navigate to the node in BloodHound, click the node, scroll down to the "Sessions" tab and expand the window
Observe the error seen in the screenshot below
Expected behavior
The application should be able to gracefully handle multiple relationships originating from the same name to the same destination node. The application should not try to render the duplicate relationship and should skip the relationship, allowing the application to draw the graph.
Screenshots
Additional context
This finding was discovered through creating a "data connector" between Crowdstrike Falcon to automatically ingest new session data every 24 hours using the advanced event search API and direct interaction with Neo4j. In this particular case, we manually uploaded session data and then ran the connector and noticed the application was not able to gracefully render the graph. This (generally speaking) shouldn't be able to occur in the wild, though I think is worth the report because it does cause the graph & application to become unusable without reloading the page.
The text was updated successfully, but these errors were encountered:
The graph design of BloodHound expects no duplicate edges between nodes. Unfortunately, this is not something we can enforce within Neo4J, so bypassing the app can result in unexpected behaviors. We would suggest modifying the integration to either update the existing HasSession edge, such as updating the lastseen date, or add an additional property to indicate the desired information.
Describe the bug
The BloodHound Web UI is unable to gracefully handle/display duplicate relationships to the same nodes. See the attached Neo4j screenshot below.
To Reproduce
Easy steps to reproduce the behavior:
Expected behavior
The application should be able to gracefully handle multiple relationships originating from the same name to the same destination node. The application should not try to render the duplicate relationship and should skip the relationship, allowing the application to draw the graph.
Screenshots
Additional context
This finding was discovered through creating a "data connector" between Crowdstrike Falcon to automatically ingest new session data every 24 hours using the advanced event search API and direct interaction with Neo4j. In this particular case, we manually uploaded session data and then ran the connector and noticed the application was not able to gracefully render the graph. This (generally speaking) shouldn't be able to occur in the wild, though I think is worth the report because it does cause the graph & application to become unusable without reloading the page.
The text was updated successfully, but these errors were encountered: