Skip to content
KitploitKITPLOIT
工具漏洞利用博客
Log in
提交
工具漏洞利用博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

订阅源联系隐私© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
TLDR — Sigma-based detection rules, log queries, atomic tests, and response procedures for monitoring and threat hunting in GitLab environments. | Kitploit
工具/GitLabGitLab/gitlab-security-oss/tldr
Defensive ToolsIntrusion DetectionLearning & EducationIncident ResponseCurated ResourcesLog Analysis
GitLabgitlab-security-oss/tldr

TLDR

Sigma-based detection rules, log queries, atomic tests, and response procedures for monitoring and threat hunting in GitLab environments.

查看仓库
311147天前尚未审核
分享
内容在请求的语言中不可用。显示英文版本。

TLDR Framework

About

TLDR (Threat, Logs, Detection, Respond) is a public collection of security detections for GitLab. Each detection is one Markdown file that explains the threat, shows the log events it produces, gives a Sigma rule, and says what to do when it fires.

The repository answers the questions you ask when something happens on a GitLab instance, in your words:

  • A GitLab security advisory landed: am I exposed (which versions, which offering and tier)?
  • Would I see it (which logs carry the signal, and is that log available to me)?
  • What do I deploy (a Sigma rule you can convert for your SIEM, and a raw query for when you have none)?
  • What do I do when it fires (response steps)?

Who this is for

  • Administrators of self-managed and GitLab Dedicated instances, who can collect the application, API, audit and Workhorse logs.
  • Owners of GitLab.com groups on Ultimate, who can stream audit events to their own destination.
  • Detection engineers who convert Sigma rules to their SIEM's language.
  • Incident responders who need the threat, the log evidence and the response steps in one place.

How to navigate

There are two folders under Detections/platforms/GitLab/:

  • Threat Detections/: behaviour-based detections (for example a new administrator account, a deploy key created, silent mode enabled).
  • Vulnerability Detections/: detections tied to published CVEs, with the affected and fixed versions.

Every file starts with a small YAML frontmatter block that states the offering, tiers, log sources and (for vulnerabilities) the affected versions. index.yaml at the repository root (with an identical index.json) lists all 43 detections in one place, and is generated by scripts/build_index.py. The frontmatter schema is documented in docs/CONTRACT.md.

Starting from an advisory

The table below is generated from index.yaml (python scripts/build_index.py --readme README.md), and --check fails when it is stale. Detection files are listed by file name; the primary detection is the entry point for each CVE. CVE ranges are checked weekly against GitLab's CVE records; see the badge at the top of the project page. Each CVE also carries last_verified.

CVEfixed inprimary detectionother detections
CVE-2026-10543719.3.8, 19.4.6, 19.5.4git_merge_tree_child_process_crash
CVE-2026-11026418.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1org_mode_render_error_burstonigmo_native_worker_crash
CVE-2026-8570618.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2local_file_inclusion_path_enumerationlocal_file_inclusion_gitlab_yml_read, local_file_inclusion_metadata_path
CVE-2026-9357719.2.7, 19.3.3, 19.4.1ci_lint_workhorse_worker_crashci_lint_scripted_client_error_burst, ci_regexp_guard_rejection, graphql_cilint_hostile_regexp, onigmo_native_worker_crash
CVE-2026-9722919.2.8, 19.3.5, 19.4.2ci_lint_workhorse_worker_crashci_lint_scripted_client_error_burst, ci_regexp_guard_rejection, ci_regexp_oversized_non_ascii_path, graphql_cilint_hostile_regexp, onigmo_native_worker_crash

Self-managed vs GitLab.com

What you can detect depends on what you can collect.

  • Self-managed and Dedicated: you can read the application logs on the host or in your cluster (production_json, api_json, application_json, graphql_json, exceptions_json, audit_json, Workhorse, Puma). Both folders apply.
  • GitLab.com: you do not have host logs. The only source is audit events streamed to a destination you control, which requires an Ultimate group. Only detections whose frontmatter lists saas in offering apply, and they read audit events only. Streamed events use event_type where audit_json.log uses event_name, so field names differ.

The log source names, paths and availability are in docs/CONTRACT.md. For GitLab's own documentation, see audit event streaming and GitLab logs.

Structure of a detection

Each TLDR detection starts with frontmatter (offering, tier, log sources, scenarios, and for vulnerabilities the CVEs and affected versions) followed by this structure:

  1. About: Overview of the threat
  2. Threat Details:
    • Technical Details/Impact
    • Business Impact
  3. Logs:
    • Required log sources
    • Sample event logs
  4. Detection:
    • SIGMA rule or equivalent
    • Raw Log Query (for environments without SIEM)
  5. Atomic Test: Instructions to reproduce the threat for testing
  6. Response: Guidance on handling the detected threat
  7. References: Additional resources and documentation

For a sample TLDR detection, see Maintainer or Owner Permission Added to a Project.

下载工具

最受欢迎

查看全部 →

发现我们社区最常用的工具。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 终极 OSINT 工具包:调查图谱、置信度评分、别名家族、地图、时间线和报告。49 个模块、400+ 个站点,无需 API 密钥。

    916
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock 一键执行应用(CVE-2026-43499)

    558
  • 3

    redforge

    cybersecurity91/redforge

    浏览器端红队工具包,包含 102 个离线工具,用于侦察、载荷生成、凭据攻击、加密、编码和交战报告。

    370
  • 4

    ARTEX

    baarai/artex

    基于LLM的多智能体自主渗透测试平台,具备规划器/执行器智能体、资产与探索图谱、MITM流量记录以及漏洞复测功能。

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT 平台,可将 Shadowserver 报告导入 MongoDB,并将其重放为交互式地图、分析、发现、公告和高管仪表板。

    317
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI原生网络安全的行动系统——在这里,意图转化为受治理的执行,证据沉淀为运营记忆,每一次操作都让下一次更出色。

    289

探索所有工具

浏览我们的工具集合

查看所有工具 →