1. 21 7月, 2023 1 次提交
    • I
      Fixed API token authentication bypassed when path contains `/healthz` · 83ca1abb
      ItalyPaleAle 提交于
      The APITokenAuthMiddleware allowed bypassing the check if the path included `/healthz`. An attacker only needed to include `/healthz` in the URL, even the querystring, to bypass the API token check, for example `/v1.0/invoke/myapp/method/something?foo=/healthz`.
      
      Additionally, this was not checking the method of the request, so requests to `POST /healthz` would cause a service invocation to happen.
      
      This fixes the issue by making the check a lot more strict. The API token check can be bypassed only if:
      
      - The path is exactly `/v1.0/healthz` or `/v1.0/healthz/outbound` (slashes are trimmed on each side)
      - The method is `GET`
      Signed-off-by: NItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
      83ca1abb
  2. 20 7月, 2023 1 次提交
  3. 18 7月, 2023 2 次提交
  4. 28 6月, 2023 1 次提交
  5. 22 6月, 2023 2 次提交
  6. 21 6月, 2023 6 次提交
  7. 20 6月, 2023 2 次提交
  8. 17 6月, 2023 1 次提交
  9. 13 6月, 2023 1 次提交
  10. 10 6月, 2023 2 次提交
  11. 09 6月, 2023 10 次提交
  12. 08 6月, 2023 1 次提交
  13. 07 6月, 2023 3 次提交
  14. 06 6月, 2023 1 次提交
  15. 02 6月, 2023 1 次提交
  16. 31 5月, 2023 2 次提交
  17. 26 5月, 2023 3 次提交