Skip to content

Commit 3e78564

Browse files
author
Omur
committed
Defining forgotten authentication
1 parent 4097948 commit 3e78564

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

src/main/java/com/webfuzzing/commons/faults/DefinedFaultCategory.java

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,17 @@ public enum DefinedFaultCategory implements FaultCategory {
122122
" Still, some heuristics could be used to flag highly suspicious cases." +
123123
" For example, if a user is blocked with a 403 to do a PUT and a PATCH on a resource, it would" +
124124
" be quite suspicious if a DELETE would work just fine on that resource."),
125-
125+
SECURITY_FORGOTTEN_AUTHENTICATION(207, "A Protected Resource Is Accessible Without Providing Any Authentication",
126+
"forgottenAuthentication",
127+
"Endpoints that require authentication must never succeed without it. If the same verb and path return 401/403 " +
128+
"when invalid credentials are used, this shows the endpoint is meant to be protected. But if a call to " +
129+
"the same endpoint with no authentication at all still returns 2xx, this is a forgotten authentication bug. " +
130+
"It means a resource that should be locked is accessible anonymously, exposing or modifying data without any " +
131+
"identity checks. " +
132+
"Detection relies on identifying endpoints that demonstrate protection (i.e., return 401/403 when accessed with " +
133+
"invalid credentials), and then verifying whether the same request, when executed without any authentication, " +
134+
"still results in a successful 2xx response. If this occurs, it reveals a critical lapse in the authentication " +
135+
"mechanism.")
126136
;
127137

128138
private final int code;

0 commit comments

Comments
 (0)