security-talent/bugskill-ai

insecure-source-code-management

Source control and artifact exposure (.git, .svn, .hg, backups, .env).

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/security-talent/bugskill-ai --skill insecure-source-code-management

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

SKILL: Insecure Source Code Management

AI LOAD INSTRUCTION: This skill covers detection and recovery of exposed version-control metadata, common backup artifacts, and related misconfigurations. Use only in authorized assessments. Treat recovered credentials and URLs as sensitive; do not exfiltrate real data beyond scope. For broad discovery workflow, cross-load recon-for-sec and recon-and-methodology when those skills exist in the workspace.

0. QUICK START

High-value paths to probe first (GET or HEAD, respect rate limits):

http
/.git/HEAD
/.git/config
/.svn/entries
/.svn/wc.db
/.hg/requires
/.bzr/README
/.DS_Store
/.env

Routing note: quickly probe these paths first; for full recon workflow, load methodology from recon-for-sec and recon-and-methodology before deeper testing.


1. GIT EXPOSURE

Detection

  • `/.git/HEAD` — valid repo often returns plain text like:
text
ref: refs/heads/main
  • `/.git/config` — may expose remote.origin.url, user identity, or embedded credentials.
  • `/.git/index`, `/.git/objects/` — partial object store access enables reconstruction with the right tools.

403 vs 404

  • `404` — path likely absent or fully blocked at the edge.
  • `403` on `/.git/` — directory may exist but listing is denied; still try direct file URLs:
http
/.git/HEAD
/.git/config
/.git/logs/HEAD
/.git/refs/heads/main

A 403 on the directory plus 200 on `HEAD` strongly indicates exposure.

Recovery tools (open source)

  • `arthaud/git-dumper` — dumps reachable .git tree when individual files are fetchable.
  • `internetwache/GitTools` — Dumper, Extractor, Finder modules for partial/corrupt dumps.
  • `WangYihang/GitHacker` — alternative recovery when standard dumpers miss edge cases.

Key files to prioritize

PathWhy it matters
.git/configRemotes, credentials, hooks paths
.git/logs/HEADCommit history, reflog-style leakage
.git/refs/heads/*Branch tips, commit SHAs
.git/packed-refsPacked branch/tag refs
.git/objects/**Object blobs for reconstruction

2. SVN EXPOSURE

Detection

  • SVN before 1.7: `/.svn/entries` — XML or text metadata listing paths and revisions.
  • SVN ≥ 1.7: `/.svn/wc.db` — SQLite working copy database (PRAGMA table_info after download).

Example probe:

http
GET /.svn/entries HTTP/1.1
GET /.svn/wc.db HTTP/1.1

Recovery

  • `anantshri/svn-extractor` — automated extraction from exposed .svn.
  • Manual: download wc.db, query with sqlite3 for file paths and checksums, then request `/.svn/pristine/` blobs if exposed.

3. MERCURIAL EXPOSURE

Detection

  • `/.hg/requires` — small text file listing repository features; confirms Mercurial metadata.
http
GET /.hg/requires HTTP/1.1
GET /.hg/store/ HTTP/1.1

Recovery

  • `sahildhar/mercurial_source_code_dumper` — dumps repository when store paths are reachable.

4. OTHER LEAKS

Bazaar (Bzr)

  • Probe `/.bzr/README` and `/.bzr/branch-format` for Bazaar metadata.

macOS .DS_Store

  • `/.DS_Store` can encode directory and filename listings.
  • Tools: `gehaxelt/ds-store`, `lijiejie/ds_store_exp` — parse .DS_Store offline.

Backup and config artifacts

Probe (adjust for app root and naming conventions):

text
/.env
/backup.zip
/backup.tar.gz
/wwwroot.rar
/backup.sql
/config.php.bak
/.config.php.swp

Web server misconfiguration signal (example: NGINX)

  • `location /.git { deny all; }` — may return 403 for /.git/ while still allowing or denying specific subpaths depending on rules.
  • 403 on a protected location can confirm the route exists; always distinguish from 404 on non-existent paths.

5. DECISION TREE

  1. Probe `/.git/HEAD` → ref: refs/heads/ pattern? → run git-dumper / GitTools / GitHacker; review config and logs/HEAD for secrets.
  2. Else probe `/.svn/wc.db` or `entries` → success? → svn-extractor or manual wc.db + pristine recovery.
  3. Else probe `/.hg/requires` → success? → mercurial dumper.
  4. Else probe `/.bzr/README` → Bazaar tooling or manual path walk.
  5. Parallel: fetch `/.DS_Store`, `/.env`, common backup extensions on app root and parent paths.
  6. Interpret status codes: 403 on directory + 200 on specific files → treat as high priority for file-by-file extraction.

6. RELATED ROUTING

  • From [recon-for-sec](../recon-for-sec/SKILL.md) — scope-safe discovery, crawling, and fingerprinting before deep VCS tests.
  • From [recon-and-methodology](../recon-and-methodology/SKILL.md) — structured methodology and evidence handling.

Note: coordinate with recon skills—set scope and request rate first, then run targeted VCS/backup validation.

같은 저장소의 Skills

더 많은 Skills

모든 Skills