Web Graph Unable to Handle Duplicate Relationships

[Sq00ky]

Describe the bug
The BloodHound Web UI is unable to gracefully duplicate relationships to the same nodes. See the attached Neo4j screenshot below.

To Reproduce
Easy steps to reproduce the behavior:

1. Pick a node, let's say a User Account (JEFF) and a Computer (WK1)
2. Use Neo4j to manually establish multiple relationships (ex. HasSession) from Jeff to WK1 two times over:
3. Execute the following neo4j query twice: MATCH (u:User {name: "JEFF@DOMAIN.COM"}) MATCH (c:Computer {name: "WK1.DOMAIN.COM"}) CREATE (c)-[:HasSession]->(u)
4. Navigate to the node in BloodHound, click the node, scroll down to the "Sessions" tab and expand the window
5. 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.

[Sq00ky]

you know, i thought this was the SpecterOps repo 🤣 I even told myself to make sure it was...