Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Feature Request: Allow searching of all captured properties

未关闭
#112 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
azure, go
领域
backend, cloud

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

Image

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.

主要语言
Go
星标
979
派生
150
平均合并
1 小时 45 分钟
30 天内合并 PR
1

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

SpecterOps/AzureHound 的其他 Issue

查看 SpecterOps/AzureHound 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。