扫描报告
20 /100
cmdb-query
查询 CMDB 资产数据,支持按主机、应用、数据库等资源类型查询
A legitimate internal CMDB query tool with hardcoded credentials in source and documentation, and disabled SSL verification — concerning but aligned with documented purpose.
可以安装
Replace hardcoded credentials with environment variables or a secrets manager, and remove verify=False unless the internal CA is trusted.
安全发现 3 项
| 严重性 | 安全发现 | 位置 |
|---|---|---|
| 中危 | Hardcoded plaintext credentials in source code 凭证窃取 | lib/query.py:14 |
| 低危 | Credentials publicly listed in SKILL.md 文档欺骗 | SKILL.md:16 |
| 低危 | SSL certificate verification disabled 敏感访问 | lib/query.py:37 |
| 资源类型 | 声明权限 | 推断权限 | 状态 | 证据 |
|---|---|---|---|---|
| 文件系统 | NONE | READ | ✓ 一致 | lib/query.py:7-10 import statements only |
| 网络访问 | READ | WRITE | ✓ 一致 | SKILL.md declares curl/jq usage; code makes POST requests to internal CMDB API |
| 命令执行 | NONE | NONE | — | No subprocess or shell execution found |
| 环境变量 | NONE | NONE | — | No os.environ access found |
5 项发现
中危 外部 URL 外部 URL
https://10.255.227.233/cmdb SKILL.md:4 中危 外部 URL 外部 URL
https://10.255.227.233/cmdb/v1/api/cloudresources/resource/instance/host SKILL.md:116 中危 外部 URL 外部 URL
https://10.255.227.233/cmdb/v1/api/cloudresources/resource/instance/application SKILL.md:124 中危 外部 URL 外部 URL
https://10.255.227.233/cmdb/v1/api/cloudresources/resource/instance/RDS_database SKILL.md:139 中危 外部 URL 外部 URL
https://10.255.227.233/cmdb/v1/api lib/query.py:13 目录结构
2 文件 · 10.2 KB · 369 行 Python 1f · 193L
Markdown 1f · 176L
├─
▾
lib
│ └─
query.py
Python
└─
SKILL.md
Markdown
依赖分析 1 项
| 包名 | 版本 | 来源 | 已知漏洞 | 备注 |
|---|---|---|---|---|
requests | unpinned | pip | 否 | No requirements.txt found; requests is used but not pinned |
安全亮点
✓ No reverse shell, C2, or data exfiltration behavior observed
✓ No obfuscation (no base64, eval, or anti-analysis techniques)
✓ No credential harvesting beyond the single service account it uses
✓ No unauthorized sensitive file access (~/.ssh, ~/.aws, .env)
✓ No supply chain risks (single requests dependency, no unpinned install)
✓ Implementation matches documented behavior — no hidden functionality
✓ Token caching with expiry logic is reasonable for an internal tool