SpecterOps / SpecterOps/AzureHound
Feature Request: Allow searching of all captured properties
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 961
- Forks
- 148
- Avg merge
- 22h 26m
- Merged PRs (30d)
- 4
Description
When parsing through the json output, certain properties are captured that cannot be queried via BloodHound or the neo4j consoles.
For example:
{
"kind": "AZAppRoleAssignment",
"data": {
"appRoleId": "01c0a623-fc9b-48e9-b794-0756f8e8f067",
"createdDateTime": "2022-08-12T14:11:25.0841466Z",
"id": "1cBV4_REDACTED",
"principalDisplayName": "Postman",
"principalId": "e355c0d5-REDACTED-f91bb0c16323",
"principalType": "ServicePrincipal",
"resourceDisplayName": "Microsoft Graph",
"resourceId": "129f86f8-REDACTED-554be743f9b9",
"appId": "00000003-0000-0000-c000-000000000000",
"tenantId": "REDACTED"
}
}
This node/relationship is captured, so AzureHound is able to identify nodes with the Policy.ReadWrite.ConditionalAccess permission
However, this query fails to return any results when it has clearly been captured by the utility.
MATCH (n:AZServicePrincipal)
WHERE n.approleid = "01c0a623-fc9b-48e9-b794-0756f8e8f067" OR n.approleid = "ad902697-1014-4ef5-81ef-2b4301988e8c"
RETURN n
It would immensely beneficial to be able to return nodes that have these properties, even if they do not currently map attack paths (CA Policies are not captured via AzureHound) to other nodes as this would allow users to identify potential targets to investigate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the AZAppRoleAssignment data in AzureHound's JSON output becomes BloodHound nodes or relationships, with attention to fields such as appRoleId and principalId. Confirm completion by querying those captured properties in BloodHound or the neo4j console, including properties that do not currently map to attack paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100