防护思路
点击放大

A general-purpose security research repository spanning browser exploit chains, post-exploitation tradecraft, identity and cloud attacks, and the assessment work that surrounds them. The contents are organized into three broad bodies of work:
Every offensi ships with a defender-side counterpart. The repository is meant to feed scheduled enterprise log-scan agents and red-team tabletop work, so breadth is intentional.
---
This repository exists to support internal security education and risk awareness. The exploit reproductions, attack chain demonstrations, and assessment tooling are built as red-team exercises that show stakeholders — including non-technical business users — what can go wrong when production systems lack adequate human o and go controls.
All materials are for educational purposes and authorized security testing only. Research was conducted under explicit written authorization. Exploit code is provided to support defensi, reproduction, and security assessment. Do not use any code or technique against systems you do not own or ha written authorization to test. See SECURITY.md for the full responsible-disclosure policy and containment architecture.
Safeguards in place:
127.0.0.0/8 or the Docker bridge). This is enforced in code by ContainmentGuard — not by con.internal: true network with no internet gateway.exec command outside of a Docker container, and every other beacon command is on a hardcoded allowlist.--plant) only installs a harmless cron heartbeat that --cleanup removes.---
A Docker Compose lab provides a fully isolated en for running tools end-to-end. All services run on an internal Docker network with no internet access, so tools that "phone home" simply talk to mock services running alongside them.
The lab can be brought up incrementally — the base make lab-up is enough for most C2 and exploit-server work, and additional mock IdPs and OAuth issuers come up targets so you only run what your scenario needs.
| Service | Port | Description | How to start |
|---------|------|-------------|--------------|
| C2 server | 127.0.0.1:8443 | Operator API + beacon protocol | make lab-up |
| Exploit server | 127.0.0.1:9090 | Serves C, recei | make lab-up |
| Target app 1 | 127.0.0.1:8501 | Simulated Databricks Streamlit app | make lab-up |
| Target app 2 | 127.0.0.1:8502 | Second target for lateral mo | make lab-up |
| Mock Entra IdP | 127.0.0.1:9100 | Device code, token, PRT SSO endpoints | make lab-up |
| Mock IMDS | 127.0.0.1:9200 | AWS / GCP / Azure metadata service mock | make lab-up |
| LLM copilot app | 127.0.0.1:8080 | Ollama-backed enterprise copilot (injection target) | make lab-llm-up |
| Mock OIDC issuer | 127.0.0.1:9300 | GitHub Actions OIDC simulation (WIF abuse) | make lab-oidc-up |
| Mock SAML SP/IdP | 127.0.0.1:9400 | SAML assertion target (Golden SAML demo) | make lab-saml-up |
| Mock Databricks | 127.0.0.1:9500 | Databricks Apps OAuth/OBO mock | make lab-databricks-up |
| AD CS lab | 192.168.56.10 | Windows DC + Enterprise CA (, host-only) | make lab-adcs-up |
Containment. tools/lib/containment.py — and its Rust counterpart in tools/rust/containment/ — is the trust boundary. It enforces loopback-only networking, non-root execution, tmpdir isolation, and Docker en detection across every tool. If a tool tries to step outside the sandbox (talk to a real tenant, reach a real metadata service, write outside the fixture root), the guard refuses before any side effect happens.
---
Each tool below ships under tools/ and has a sibling detection/ directory containing Sigma rules, KQL queries, or other defender-side guidance for the same technique. The brief descriptions are intentionally compact — each linked README expands on usage, lab requirements, and detection.
http_polling/, websocket/, grpc/, passi/, dns_o/, http3/ for QUIC, doq/ for DNS-o, and teams-graph/ mocks). Each ships with Sigma / KQL detection alongside the offensive code.corp.lab.local lab domain.himds pipe DACL); Exchange hybrid evoSTS token forge.QUERY_HISTORY. Talks to mock-snowflake on 9600.sub abuse, Golden SAML, Silver SAML (secondary cert), SyncJacking via ImmutableId takeover, E de 2026 PhaaS (Broker client ID FOCI path), FOCI Conditional Access bypass, PRT extraction via de, and a CloudTrail-blinding catalog. Talks to the lab mocks: mock-oidc (9300), mock-saml (9400), mock-entra (9100/9102).mock-snowflake on 9600.cloud-identity/.EXPLOIT_LAB_KERNEL=1 and a kern-lab-* hostname, by safety_harness.py before anything dangerous runs.mock-aitm-proxy 8100 / mock-m365-login 8101), Sneaky2FA's browser-in-browser , and Rockstar2FA — plus reference docs for E. Importantly, this section also documents the defender controls that actually break these kits: passkey mitigation and Conditional Access token protection.mock-entra). Tracks how these chains e from 2023 through 2026.pull_request_target ("pwn_request") simulation against a mock on 8120, the UNC6426 OIDC chain (mock-oidc 9300 → mock-imds 9200), self-hosted-runner persistence, and the tj-actions-class supply-chain compromise pattern..pth persistence simulator with a runtime-detector defender tool, exercised against mock-pypi on 8111.with_spoofed_stack() RAII wrapper for hiding suspicious frames.OutputSandbox capture. See also tools/bofs/ for safe BOF implementations that exercise the loader.mock-copilot on 8090.mock-agentforce on 8091.mock-snowflake on 9600 and mock-snowflake-mcp on 9620.m365_copilot channel for the Copilot-specific surface.EXPLOIT_LAB_K8S=1.EXPLOIT_LAB_EBPF=1.cd tools/rust && cargo build --release.---
The repository tracks Chrome and Firefox CVEs from 2024 through 2026 — patch analysis, triggers, and complete chains. The full table is collapsed below; for the canonical index with implementation status, see c.md.
<details>
<summary>C across Chrome and Firefox (2024–2026) — click to expand</summary>
| CVE | Target | Year | Technique | Level | Path |
|-----|--------|------|-----------|-------|------|
| C | Chrome V8 Maglev | 2024 | OOB Write | ACE | c/2024/C/ |
| C | Chrome V8 Wasm S128 | 2024 | Type Confusion | ACE | c/2024/C/ |
| C | Chrome V8 Object Transitions | 2024 | Type Confusion | ACE | c/2024/C/ |
| C | Chrome Wasm JSPI | 2025 | Sandbox Escape | ACE | c/2025/C/ |
| C | Chrome ANGLE WebGL2 | 2025 | UAF | UAF | c/2025/C/ |
| C | Chrome V8 Property Array | 2025 | Type Confusion | ARW | c/2025/C/ |
| C | Chrome CSS FontFeature | 2026 | UAF | UAF | c/2026/C/ |
| C | Chrome Skia Glyph Atlas | 2026 | OOB Write | OOB | c/2026/C/ |
| C | Firefox SpiderMonkey | 2024 | Type Confusion | Trigger | c/2024/C/ |
| C | Firefox AnimationTimeline | 2024 | UAF | UAF | c/2024/C/ |
| C | Firefox JIT Range Analysis | 2024 | BCE | ARW | c/2024/C/ |
| C | Firefox Pri JS | 2024 | Sandbox Escape | ACE | c/2024/C/ |
| C | Firefox IPC | 2025 | Sandbox Escape | Trigger | c/2025/C/ |
| C | Firefox Promise | 2025 | OOB | OOB | c/2025/C/ |
| C | Firefox IonMonkey BCE | 2025 | OOB | ARW | c/2025/C/ |
| C | Firefox Wasm GC | 2026 | UAF | ACE | c/2026/C/ |
| C | Firefox Wasm JIT | 2026 | Type Confusion | Trigger | c/2026/C/ |
Level key: ACE = arbitrary code execution, ARW = arbitrary read/write, UAF = use-after-free demonstrated, OOB = out-of-bounds access, Trigger = bug trigger only.
</details>
---
For more granular indexes, see tools/, docs/analysis/, and docs/methodology/ — each has its own README.
---
1. Clone the repository and install lab dependencies: pip install -r requirements-lab.txt
2. Bring up the contained lab (requires Docker): make lab-up. Use make lab-status to confirm e is healthy and make lab-down when you are finished.
3. To run tools locally without the full lab, start the C2 server in one terminal (python3 tools/c2/server.py) and a beacon in another (python3 tools/c2/beacon/beacon_client.py).
4. Browse cves/ for specific C. Each C contains its own README with setup instructions.
5. For the Databricks assessment dashboard, see the section below.
---
A secondary deli in this repository is an interacti assessment of the Databricks Apps platform, prepared for security leadership. It lives at reports/databricks-apps-assessment/ and is rendered as a Streamlit dashboard.
cd reports/databricks-apps-assessment && pip install -r requirements.txt && streamlit run app.pysrc/ (_00_header.py … _99_dispatch.py); python build.py concatenates them into the deployable app.py. Edit the src/ files, never app.py directly. python build.py --check the build is up to date.Findings the report covers include OAuth On-Behalf-Of (OBO) token-abuse paths in Databricks Apps, the Databricks app identity chain and ser exposure, detection gaps in the Databricks audit logs, and concrete recommendations for monitoring, go, and access-control impro.
---
Dual-licensed under Unlicense and MIT.
开发语言:Python
Star 数:13
该项目属于防护思路方向的开源资源,代码结构清晰,适合安全研究人员学习参考。项目围绕Security research and exploit development: vulnerability analysis, exploit chain implementation, post-exploitation tradecraft, and defensive assessment tooling. Covers browser engines, persistence mechanisms, credential harvesting, C2 patterns, and AI-accelerated attack automation.展开,提供了可运行的实现,对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。
从技术实现角度看,此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论,梳理项目的初始化流程、核心模块职责与数据流转,逐步掌握其中的技术细节与设计思路。
1. 下载源码压缩包,解压到本地环境。
2. 根据项目类型准备对应的运行环境与依赖。
3. 按照 README 中的步骤完成配置与部署。
4. 在隔离的测试环境中运行验证,避免影响生产系统。
本资源来源于开源社区,仅供安全研究、技术学习与合法授权范围内的攻防演练使用,请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。
| 资源标题 | exploits - Security research and exploit development: vulnera |
| 所属分类 | 防护思路 |
| 发布作者 | admin |
| 发布时间 | 2026-10-06 00:11:29 |
| 下载权限 | 免费下载 |
| 附件数量 | 2 个下载链接 |
| 浏览次数 | 155 |
| 讨论数量 | 0 |
| 主题状态 | 正常讨论中 |