Files
metasploit-gs/lib/msf/core/exploit/remote
adeherdt-r7 a3a24418a8 MS-9517 Jenkins Login Scanner
Jenkins does not implement Authentication challenges.

By default, Jenkins responds with a HTTP 403 FORBIDDEN response, and does not include the `WWW-Authenticate` header.
This causes problems with the underlying http client, as this one expects the challenge to come forward and resend
the request with the auth header.

By changing the code to look for the HTTP 403 response, and setting the default URL to the correct login validation endpoint
Pro will have an easier time to investigate whether Jenkins can be bruteforced or not.

The original code checks for a 401 response only.
Overwriting the behavior for Jenkins allows us to handle this use-case properly and report the correct behavior.
2024-08-13 11:16:01 +02:00
..
2024-08-13 11:16:01 +02:00
2023-09-24 17:42:00 -04:00
2020-12-07 10:31:45 +00:00
2024-03-25 11:53:23 +00:00
2024-03-25 11:53:23 +00:00
2023-11-13 21:41:28 +00:00
2023-12-04 17:55:11 +00:00
2020-12-07 10:31:45 +00:00
2021-02-08 12:24:12 +00:00
2020-12-07 10:31:45 +00:00
2021-02-08 12:24:12 +00:00
2020-12-07 10:31:45 +00:00
2020-12-07 10:31:45 +00:00
2024-06-18 17:47:56 -04:00
2022-02-03 16:09:49 -05:00
2024-04-24 15:06:36 -04:00
2020-12-07 10:31:45 +00:00
2021-02-08 12:24:12 +00:00
2020-12-07 10:31:45 +00:00
2023-09-24 17:42:00 -04:00
2023-09-24 17:42:00 -04:00
2020-12-07 10:31:45 +00:00
2021-02-08 12:24:12 +00:00
2020-12-07 10:31:45 +00:00
2020-12-07 10:31:45 +00:00
2020-12-07 10:31:45 +00:00
2023-09-24 17:42:00 -04:00
2022-03-24 21:59:02 +00:00
2020-12-07 10:31:45 +00:00
2021-02-12 14:33:05 +00:00